Multi Level Cascade Select Plugin forgets saved values on Edit screen

[J Thomas]

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.)

[Brent Kennedy]

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:

$(slaveSelector).show();
clickFirstVisible(slaveSelector);

To:

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

[Aviva]

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

[Pandu Ranga]

Yes, it is resolved

[suryavani bhallamudi]

Plz help me i am also looking for the solution