I have a project with multiple issue types, all of which use the same edit/view screen and screen configuration. However they use and have to use different workflows due to approval processes.
I have enabled Issue type edit but get a message that only a move will be allowed. This is a cumbersome method and something that was not required on our old system.
Is there any way that I can handle this scenario without the use of the move, given the use of multiple workflows?
Thanks for the answers.
Looks like i am going to have to live with the use of move but I will try to use common workflows where possible to prevent the need to use move in the future.
Couldn't JIRA be enhanced to allow this update to be supported provided the configuration states want part of the alternative workflow it should be placed in.
The enhancement requests to do this have mostly been shut down as "won't do" by Atllassian, as the checks for data consistency need to be done when moving issues. Some are still open (like the simple status to status I mentioned below)
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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