We just moved to JIRA 7.0.11 from 6.3.1 and already started to see issues to our workflow setup. I am trying to change project type for an existing issue and the process does not take in all the mappings. For every project change that I try to do, it stops at the screeen where I need to enter the Componenet/s field value.
As a workaround, turning off the behaviors will allow me to make the move successfully.
Below are the errors and debug statements of moving the issue on JIRA;
I would like to know if there is any way to validate the behaviors in the production instance of JIRA? Do I need to change any configuration on the serverside script of behaviors?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
This September 6-7, hundreds of Atlassian App developers will flock to Barcelona Spain to build skills, discover product roadmaps, meet face-to-face with the Atlassian team, and learn how to extend t...
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