Unable to select the newly edited value for project specific field

[Bhupinder Pooni]

Steps to reproduce the issue: 1. Rename/Edit an existing value for a Project Specific Select Field. 2. Open an existing issue (or create a new issue), select the new (edited) value for the above field. Note: The new value is available to be selected) 3. Submit the change. The field will show the old value (the one prior to the recent edit)

See snapshots for more information. I have even tried manually re indexing the JIRA. The problem persist.

Version: 2.4.2

[Holger Schimanski]

Many thanks for reporting! What is shown in the issue history? Can you also try to rename via regular JIRA administrator user interface editing the option value for the context of that project?

[Bhupinder Pooni]

• Issue history shows the old value (not the new edited value)
• If I edit the field value from the JIRA administrator user interface, the new value is available & is select-able right away. In fact it updates the issue with old values automatically.

[Holger Schimanski]

When you edit an option value via the project administrator Project Specific tab and after edit then go somewhere else and come back, do you see the new (edited) value or again the old value? I am asking because I have the feeling that the edit of the option value is not really submitted to the backend.

[Bhupinder Pooni]

I see new edited value, even the new edited value is available in the drop-down on the issue after the edit. But when i select the new edited value & submit the issue. It displays old value. What I am thinking is that editing thru the Project Administration->Project Specific tab doesn't get indexed somewhere in JIRA backend.

Visually in the drop-down new values is shown but as soon as i select & submit the issue it is being replaced with old value. Another observation i had when user reported this issue few days back was that over time (possibly overnight) it fixes itself.

[Holger Schimanski]

In fact it updates the issue with old values automatically.

Yes, this is how it should work.

If I edit the field value from the JIRA administrator user interface, the new value is available & is select-able right away.

This is how it should work via project administrator user interface from Project Specific as well.

I need to go into review of my code. Because it is holiday season here, you need to wait for a fix probably until beginning of August. I hope this is not too critical for you.

[Holger Schimanski]

After review of my code compared to JIRA administration code I could identify the problem and had to modify my code from

tmpOption.setValue(aProjectSpecificOption.getValue());

to

tmpOptions.setValue(tmpOption, aProjectSpecificOption.getValue());

Thank you very much for reporting! Fixed in version 2.4.3 of Project Specific Select Field plugin.

Best regards, Holger

[Bhupinder Pooni]

We are able to validate the fix in our test environment. Thanks for the quick turnaround.