We did a work around by creating a status called 'fix it' and creating a transition from every status to it and from it to every status. Then we protected the transition so only the project lead could execute it and they were forced to select a reason from a select list with values like Wrong issue updated, new information, and a couple more. Then the manager was sent an email when the transtion was executed. We had found it was usually sloppy work that caused the issue to be moved incorrectly and the need to use it dropped off when managers started asking why issues were being handled incorrectly.
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