On change of issue type, multi-select custom field does not behave like components/versions fields

Similar question was asked in this thread, https://answers.atlassian.com/questions/43534 before. But still hitting this issue after using the suggested answer, 

<script type="text/javascript">
new AJS.MultiSelect({
element: $("#customfield_XXXXX"),
itemAttrDisplayed: "label",
errorMessage: AJS.params.multiselectComponentsError


Any ideas how to fix this? Any help will be appreciated.

1 answer

0 votes

That answer is from 2012.  More recent versions of JIRA are preventing the injection of javascript because it breaks things in interesting ways (including introducing security holes).  You could try it in the announcement banner, but I'm not sure the code is valid any more, given its age.

Thanks Nic for your response.


Please is there any other safe way I could achieve this? my JIRA instance version is 7.0.0. and will upgrade it soon to 7.1.7 version and I need my multi-select custom field to behave like component/version fields.

any suggestions or solution will be highly appreciated.

I don't know of any way to do this, other than creating custom field types that can use the javascript you need.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

1,071 views 4 9
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you