We just upgrade from JIRA 5.0 to JIRA 6.1. We keep the security level (the numeric value) in each user's property and then we use the misc workflow extension to set the "Security Level" equal to the user's property which has that numeric value for the Security level on the Create Issue. Worked perfectly in JIRA 5.0.
Atlassian did a fix on defaulting the security level, not sure it's related. HELP...this is messing up all our users!!
Resolution was to put the set Security Level from user priority as Step 1 in the post workflow BEFORE the Issue is created initially. This was definitely some sort of change from JIRA 5.0 to 6.1 because it used to be after "Creates the Issue initially". Thanks David for your patience and testing!
Can you please create a support request on our issue tracker at https://innovalog.atlassian.net? Please include as much information as possible: JMWE plugin version, log excerpts showing any error related to com.innovalog.jmwe, screenshot of the list of transition post-functions, etc.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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