Average time an issue needs to change status

Question

Hello Atlassian Community!

I would like to know how much time in average an issue needs to transition from one status to another, i.e, from In Progress to Approval Pending, or for example when a field issue changes and the issue is transitioned to "Done".

I can't seem to find the proper way to gather the data using the Reports tool.

Could anyone help me out?

Thank you and have a great week start!

Sergi

Emre Toptancı [OBSS] · Answer

Hello @Sergi Ortega ,

The data you need is available in each issue's history but Jira does not give this as a ready-to-use report. The closest you can get is using a Control Chart or a Cumulative Flow Diagram. Both are available as part of Jira Kanban Boards. They paint an overall picture but they don't give you the chance to work with individual issues. They also have limited flexibility in terms of report parameters.

To get what you want, you need to use a marketplace app. Our team at OBSS built Timepiece - Time in Status for Jira for this exact need. It is available for Jira Server, Cloud, and Data Center.

Time in Status basically allows you to see how much time each issue spent on each status and on each assignee.

The app has Consolidated Columns feature. This feature allows you to combine the duration for multiple statuses into a single column and exclude unwanted ones. It is the most flexible way to get any measurement you might want. Measurements like Issue Age, Cycle Time, Lead Time, Resolution Time etc.

For all numeric report types, you can calculate averages and sums of those durations grouped by the issue fields you select. For example total in-progress time per customer (organization) or average resolution time per week, month, issuetype, request type, etc. The ability to group by parts of dates (year, month, week, day, hour) is particularly useful here since it allows you to compare different time periods or see the trend.

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. It supports both Company Managed and Team Managed projects.

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. And the app has a REST API so you can get the reports from Jira UI or via REST.

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.)
* 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

Bill Sheboy · Answer

Hi @Sergi Ortega

Are you asking about calendar time in status or something else...such as the time tracking fields?  If you mean calendar time...

You noted trying the built-in reports in Jira.  Did you try using Atlassian's interpretation of a control chart, and selecting just your fields of interest and timeframe?  Please look here for information on how to configure that report as that should provide what you asked: https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-control-chart/

Kind regards,
Bill

Karolina Wons_SaaSJet · Answer

Hello @Sergi Ortega

As an alternative, you can try Time between Statuses developed by my SaaSJet team. It shows the time it takes an issue to move from one status to another.

You can generate a report based on the time between statuses and export it to the Excel file.

And then choose an "Average" option in the Excel file and get the average time an issue needs to change status.

Hope it helps.