I have setup Jira such that "Support Issues" have a different workflow to the regular development tickets. This is because they simply have different statuses due to the way they are handled internally.
However, one of the outcomes of a support issue is that it could require development to fix a bug / implement a new feature. So what i am trying to do is have a way such that if a "Support Issue" needs development and hence needs to get into the development workflow, to have a way to achieve this using the transition buttons for the ticket.
The way we are currently handling this case is to use the "Move" function which works, but its just more screens then it needs and i'm trying to simplify the process.
Is there any way to transition a ticket between 2 seperate workflows without using the "Move" function? I have tried having the same status in both workflows and then trying to change the Issue Type from "Support Issue" to "Bug" , but that didnt work :)
I dont mind buying an add-on if there is something that handles this case.
Hmmm actually i found in the "Related Questions" pretty much what i am asking.
So basically, it seems that what i am after is quite complex to achieve and is technically possible but requires development of an add-on that doesnt exist yet.
So for now, it looks like i either need to "Merge" the Support and Development workflows into 1 or keep using the "Move" method we are doing now.
I can confirm what you've found if it helps.
Moving issues from one type to another is very complex because all the configuration is hung off project/issue type, and that's why you have to go through several steps to ensure data integrity. As you've found, no-one has written a publically available post-function or process to do it automatically.
Thanks - getting comfirmation does help :)
In our particular situation, the moving between workflows should actually be quite simple because we dont have any differences between ticket requirements between the 2 workflows - so i may look to handle this myself - but it will only work in our particular situation where there is no seperate ticket information between the workflows.
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