Question on implementing a transition between statuses

Mike Albanese

In a bug/story ticket workflow, I want to add a new step, or transition, between my "QA Failed" status and "Blocked" status, so that the user has to enter a reason for failing the ticket before it transitions to "Blocked".

Ideally, as soon as the user selects "QA Failed", they would be presented with a single-selection list of "reasons for failure" to choose from. For the sake of metrics gathering, that reason would need to stay with the ticket for future access through a JQL query. And of course, because the same ticket can be failed multiple times, and for different reasons, the solution would need to keep a record of each instance for the same reason.

If someone can offer guidance or suggestions on how to implement such a thing it would greatly appreciated.

Thanks in advance.

Mikael Sandberg

If you need to keep a record, I would assume other then just the history, you would need two fields for this. This is something similar to the approval process that I wrote about here. Here is my solution for it...

Create a new screen that has the reason for failure field on it. Assign that screen to your new transition. Next I would create an automation that triggers on the transition from QA Failed to Blocked will add the reason for failure, the user that triggered the automation and a time stamp. Since you need to query on the reason for failure, I would as a post function when transitioning to QA Failed reset it, that way the user would have to select a new value when transitioning to Blocked. The other option is to inform the user to pick a new value if needed and just leave it as is.