I have a workflow that simplified looks like this: Working - Testing - Release and I'm wondering if there is a way to find out how often Issues with status Testing are transitioned backwards to 'Working' instead of forward. Is there any Report on this?
Hi @Lisa Zanini
For a readymade solution, to get this data you can try out our app.
The add-on provides the time in each status for the entire lifecycle of the issue and you can filter by issue type as well. You can also combine your statuses to define your lead/cycle/resolution time and also extract the transitions history of the issues. The main features of the app are as below
Hello @Lisa Zanini
As an alternative, you can try Time in Status for Jira Cloud, developed by my SaaSJet team. It generates status time reports.
This add-on includes a Transition Count report, that shows how much times an issue has moved to each status (Working - Testing - Release).
Is that what you need?
Hi @Lisa Zanini
With the simple workflow you describe, you could build tracking for this yourself with automation for Jira rules rather than purchasing an addon app. And, you could decide how you want alerting/reporting to work.
For example, perhaps you just want to remind the team that something has moved backwards, alerting all to take action. (After all, the things further to the right-side of the board are the things closer to release and so need action sooner.) Such a rule would be:
If you wanted to track the frequency of such things, you could log the occurrence in a custom field or entity property (allowing reporting with JQL filters) or in a comment (allowing reporting with automation rules and preserving a more visible history.)
To learn more about automation for Jira, please look at this documentation and example library:
Hello @Lisa Zanini ,
The data needed for this report is available in each issue's history but Jira does not provide this functionality out-of-the-box. If you are happy with serious custom development, you can try getting this data via REST API (changelog endpoint) and do the calculations yourself.
If you are OK with using a marketplace app, our team at OBSS built Time in Status app for this exact need and more. It is available for Jira Server, Cloud, and Data Center.
Time in Status allows you to see how much time each issue spent on each status or each assignee.
The app also has Status Count and Transition Count reports that show the number of times each status and each transition was used respectively.
For all numeric report types, you can calculate averages and sums of those durations grouped by the issue fields you select. For example, "total reopen count per user" or "average reopen count per component, issuetype, label etc."
And the app has a REST API so you can get the reports from Jira UI or via REST.
The app calculates its reports using already existing Jira issue histories so when you install the app, you don't need to add anything to your issue workflows and you can get reports on your past issues as well.
Time in Status reports can be accessed through its own reporting page, dashboard gadgets, and issue view screen tabs. All these options can provide both calculated data tables and charts.
Using Time in Status you can:
Hi, Jira users! Do you use Jira alongside Microsoft Teams? We want to hear how you’ve used the power of Jira Cloud and Microsoft Teams (via the Jira Cloud for Microsoft Teams app) to achieve a team...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events