When using auiSelect2 in a custom field, opening the select-overlay will close the quickedit-selection. This behavior happens only in Service Desk Projects, software projects work just fine.
The Velocity-Template used to create the edit-view of the custom field is also attached as a minimal sample.
The behavior does not appear when using the regular edit issue screen.
The following minimal example for a customfield editing-template causes the problem to happen for me:
Iāve raised this issue as [AUI-5357] - Ecosystem Jira. Thanks for the detailed explanation of the problem! Iām not sure what the cause is at this stage, so Iāll investigate and get back to you once I know more.
In the meantime, could you let me know the version(s) of Jira and Jira Service Desk you are using? It would also help if you could check what version of AUI is present on those pages. You can check the AUI version by inspecting the <body> tag and checking the value of the data-aui-version attribute.
Hi @daz,
thank you for the help, I will keep an eye on this ticket.
Jira is version 8.13.0, JSD is 4.13.0. I will try and update those to the newest version and see if the error persists. AUI is version 9.1.0.
Another thing that i noticed: If i set the AUISelect2 to accept multiple values, quickedit only closes after actually selecting one value. No idea if that means anything.
Edit: I have confirmed that this also happens with Jira 8.16.0, JSD 4.16 and AUI 9.1.4.
The default blur trigger in Jira will finish an inline edit whenever an input element inside its DOM is blurred.
The select2 component renders DOM elements outside of the inline edit fieldās DOM, which makes the default blur trigger inappropriate for the field.
Hereās the mystery: by default, the default blur trigger should not be enabled for custom fields; it should be up to you to either opt-in to the default blur trigger or specify your own. However, it seems this default blur trigger is getting used on the JSD issue screen.
For this reason, weāre forwarding the bug on to the JSD team to investigate why this default blur trigger is getting used.
Thank you for your replies. I am watching and following the linked ticket and will implement the suggested workaround next time i touch the plugin in question. I will let you know then!