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?
I'm afraid it needs to go through "move" to check all the data is valid. You'll have to make the workflows the same, or live with a "hard" move.
+1'ed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Although I do wish they'd code for "oh look, the current status of the issue exists in both workflows, so I can do this".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign 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)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.