UserPicker popup dialog vs Inline Editor

[Chris Kent]

Hi,

Users are starting to complain that the UserPicker (Single User) behaves differently depending on the Issue type.

For Epics, Stories, on the View screen, when the UserPicker field is clicked, must use the Edit button next to it, it actually opens up the Configured edit screen, and users have to scroll around to find the field to update it.

However for Bugs, Tasks, Improvements issue, when clicking on the field, it simply allows the field to be changed inline. The desired behaviour.

Why is this behaviour different and how can I fix this bug so that the inline editor feature is always used. It seems like it is related to the Greenhopper plugin???

[Daniel Ebers]

Hi @Chris Kent

could you please confirm there is indeed an installation of Script Runner in your instance?
I was able to observe very similar when there was a Script Runner 'behaviour' defined for a field.

In case this is the right guess - could you probably remove temporarily any behaviours from the field(s) and double check?

Regards,
Daniel

[Chris Kent]

Hi @Daniel Ebers ,

Yes, you are right, we have three behaviours for this field that acts irrationally.

Two of the behaviours tries to pre-fill the value, based on the issue type.

Another behaviour tests to see that the value has been filled in.

I'm still curious why the behaviour is erratic and not consistent?

Should I reach out to the App developer? Is this a known bug?

[Daniel Ebers]

I can't tell if this is a bug. What you are seeing, a not consistent experience, is something I can see also when configuring a field similar to what you say.

From what we could spot it is just a limitation/way of design when using behaviours like this. Perhaps it was not possible to code it any different than that.

[Chris Kent]

Hi

Another revelation... I now have the same issue open in 2 different browser tabs, both the old User Picker and new User picker fields are shown on the View screen.

Now, in one tab, both the User Pickers behave as expected, clicking them uses inline editor (no pop-up).

However, in the second tab, looking at the same issue, when I click on the old User Picker field, it opens up a dialog screen (Edit Issue Screen), whereas the new User Picker field works as expected -> inline edit.

WTF????

[Chris Kent]

Hi,

I just had another piece of insight, it is not related to the issue type, we just introduced a new User Picker field, and on a Story issue, while in the View screen, clicking the old User Picker field, causes a pop-up dialog, however the new User Picker field works inline as expected.

Could there be some old behaviour be stored in the Database?

How can we fix the old field to work inline as expected? Why is it different based on the issue type?