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.)
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.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Atlas Camp is our developer event which will take place in Barcelona, Spain from the 6th -7th of September . This is a great opportunity to meet other developers and get n...
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!
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