How to find out how often issues transitioned backwards?

[Lisa Zanini]

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?

[Rahul_RVS · Accepted solution]

Hi @Lisa Zanini 

For a readymade solution, to get this data you can try out our app.

Time in Status Reports 

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

• More than 8 types of Time in Status Reports. Excel Export available for all status reports.
  
  • Time in Status
  • Time with Assignee
  • Time in Status with Assignee
  • Time with Assignee per Status
  • Status/Assignee Count
  • Multiple Transition Reports
  • Avg Time in status reports
  • Status Change Dates Report
• Status grouping
• Save your reports
• CSV Export
• Multiple chart types
• Dashboard Gadget

[Karolina Wons_SaaSJet]

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?

Regards, Karolina

[Jacob Vu]

Hi @Lisa Zanini

You could create a filter with JQL and then use it in a report/dashboard to help you.

Something such as: "status was Testing AND status = Working"

Jacob

[Bill Sheboy]

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:

• trigger: transitioned from Testing to Working
• action: email (or Slack message) the team to alert them

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:

• https://www.atlassian.com/software/jira/guides/expand-jira/automation
• https://www.atlassian.com/software/jira/automation-template-library#/
• https://community.atlassian.com/t5/Automation-articles/Jira-Automation-all-the-resources-you-need-in-one-page/ba-p/1388465

Kind regards,
Bill

[Emre Toptancı _OBSS_]

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 Timepiece - Time in Status for Jira 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:

• See how much time each issue spent on each status, assignee, user group and also see dates of status transitions.
• Calculate averages and sums of those durations grouped by issue fields you select. (For example, see average InProgress time per project and per issue type.)
• See the number of times each status and each transition was used.
• Export your data as XLS, XLSX, or CSV.
• Access data via REST API. (for integrations)
• Visualize data with various chart types.
• See Time in Status reports on Jira Dashboard gadgets

Timepiece - Time in Status for Jira

EmreT