New multiselect AUI Select 2 UI didn't apply when creating issue from dashboard

[arcaneliu]

After update to 2.5.2, if the project doesn't have any option in the previously created multiselect project specific field in 2.5.1, everything goes fine. The new UI like JIRA version field is displayed normally.

But if there is already option values in the fields, and then old style UI is displayed.

Please have a look and provide the solution if possible.

Thanks very much

[arcaneliu]

Further test feedback: 1. Problem only happen while hit "Create" button from Dashboard, it hit "Create" button from project board, it's ok. 2. Reindex, clear browser cache, reboot server don't help 3. Remove fields from screen and then add them back, the issue is still there 4. Delete / disable some option values, the issue is still there 5. Don't know if this is due to the jsp cache on the server (since don't know how to clear cache on the server so that not trying this)

Thanks very much

[Holger Schimanski]

Many thanks for reporting! The conversion from regular to select2 custom field is done via JavaScript, but this is currently only added to view issue and create issue context. Looks like creating an issue starting from dashboard is not seen as create issue context. I will investigate further and provide an update one I can see the solution.

Best regards, Holger

[arcaneliu]

Looking forward to the new release.

Thanks a lot

[arcaneliu]

Hi Holger,

Could you help to provide some update about this topic?

Thanks very much

[Holger Schimanski]

Sorry, I was in the last steps to finalize a new add-on Version Manager for JIRA.

I will release a bugfix by end of March.

Best regards, Holger

[arcaneliu]

No problem.

Now it's clear about the plan.

Thanks very much

[Holger Schimanski]

Bugfix released as version 2.5.3.

Best regards, Holger

[arcaneliu]

Hi Holger,

Thanks for the new release.

I am just released from other task and did a quick check on the dev server for this. It looks good.

I will playing around for a little more and then deploy on the production server.

Thanks again, Arcane