Edit Issue Screen error

Question

Hi,

We noticed a strange behavior in our Edit issue screen lately. We have a custom field named Sprint Goal in our issue type Work/Story which is of type Single-select dropdown. Suppose the custom field Sprint goal already has a value "Goal1" assigned to it. Now, when we open the Edit issue screen to reset/change the value of any custom field (and not the Sprint Goal in this case), we see that the value of the Sprint Goal in the dropdown is shown as None and not the value that was already set. If we change the value of our other custom field and fail to notice the changed value for the Sprint Goal and save the issue, the sprint goal is getting changed (which we didn't mean to change actually).

Is there any reason, that the value of the dropdown (Sprint Goal) is not getting set properly when we open the Edit issue screen ? I'm unable to find the reason behind this behavior.

Thanks,

Neha

Ivan Tovbin · Answer

For PowerScripts check out Live Fields settings. See if there are any scripts "attached" to your project, and then check what those scripts do if any.

For Scriptrunner check out its Behaviours functionality (Administration > Add-ons > Behaviours)

Nic Brough -Adaptavist- · Answer

I am pretty sure that they are.  Jira has nothing built into it that can make one field dependent on another (the only thing that does is a "cascading select", which is not what you are describing here)

I can't speak for Powerscripts, as I don't use it.   But for ScriptRunner, if it is the problem, you will find something in Admin ->  Behaviours.  You should see that every Behaviour has a "context" which lists what projects it is active in, and if you think it might be a Behaviour, you can test it by changing the context so it does not cover the current project and trying the fields again.

Neha Sharma_9bogmy · Answer

Hi Ivan,

We do use Scriptrunner and Powerscripts but not really sure if they are manipulating the custom field by some means or not. I'm pretty new to all this but I'll try to find out if the custom field is being used by some plugin or not.

Would you suggest some approach as to how I should debug this issue?

Thanks,

Neha