Multi Level Cascade Select Plugin forgets saved values on Edit screen

We're testing JIRA 4.4.5 with JMLCS 2.5. We've found that if you edit an issue that has a JMLCS field on the Edit screen then only the first level is defaulted to the existing saved value and all other levels forget their saved values.

This means that data can be lost without the user realising when the edited issue is saved.

This doesn't happen if the screen is shown during a transition, only when clicking on the issue Edit link.

Any chance of a fix any time soon?

(It seems a bit weird to raise plugin bugs here but this is where the Plugin Exchange directs you.)

3 answers

This is an issue with jquery execution order. Edit multilevelcascadingUtil.js (in ATLASSIANHOME/includes) and place the code below (based on clickFirstVisible) in place of the call to clickFirstVisible(slaveSelector) in the dynamicMultiLevelSelect function. This makes it execute the jquery calls in the correct order for the plugin to work as expected.

change from:



$("option:first", slaveSelector).each(
function() {
$(slaveSelector).attr("selectedIndex", this.index);

Plz help me i am also looking for the solution

Does anyone know if this issue was resolved for Jira 5?

Yes, it is resolved

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Feb 07, 2019 in Marketplace Apps

A Timeless Love Story

It started as any story starts, on a normal, rainy day.   Admin meets App, and her name was Klok2, and like any first relationship we were both trying to make it work but neither one knew what...

441 views 8 26
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