How can I run reports on time spent in a given status?

[Christopher Marsh]

Hi there folks, I hope you're all enjoying a great start to your week. 

I need to report on the time that tickets spend in different statuses, in aggregate and per user, as metrics for OKRs. I also need to know how long tickets take to get from one status to another, again in aggregate and per user. Can anyone direct me how I can do this, please? Thanks a million!

Cheers, Chris 

[Julia Shcherbyna _SaaSJet_]

Hi @Christopher Marsh 

An add-on Time in Status For Jira Cloud has been developed especially for this task.

Here you can create all reports you need

• reports on the time that tickets spend in different statuses, in aggregate and per user, as metrics for OKRs.
• how long tickets take to get from one status to another, again in aggregate and per user.

Try an online demo without installing to understand better how it works. 

Regards

[Christopher Marsh]

Hi Julia, thanks a lot for the recommendation, I'll take a look.

[Aron Gombas _Midori_]

Using our Better Excel Exporter app you can create every sort of pivot tables and pivot charts in Excel from:

1. time spent in each status
2. time from creation to resolution
3. time from creation to first comment
4. (plus your custom time metrics here)

The app exports every sort of issue fields from assignee to project which you can use as report dimension. It also has support for "how many times an issue entered each status" type of calculations.

You may want to try it. Disclaimer: I'm a developer working on this app.

[Christopher Marsh]

Thanks Aron, this looks interesting - I'll have a play around with it.

[Janis Plume _eazyBI_]

Hi,

eazyBI app for Jira allows such reports with drag-and-drop. You can have averages per project, user, and many other standard and custom fields in Jira:

Kindly,

Janis, eazyBI support

[Emre Toptancı _OBSS_]

Hello @Christopher Marsh

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.  

You can combine statuses into Consolidated Columns to see the total of multiple statuses as a single value.

The app also has Duration Between Statuses report that shows the duration between two statuses.

    

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, 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.)
• 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

[Mehmet A _Bloompeak_]

Hi @Christopher Marsh ,

Unfortunately, what you are looking for is not possible with the built-in functionalities of JQL. Because JQL can not make calculations and you need status time calculation.

For this exact need we developed Status Time Jira app. It provides reports on how much time passed in each status. By grouping statuses you can get cycle time(E.g from in progress status to done status). You can also export the report as CSV and open it in excel.

Once you enter your working calendar into the app, it takes your working schedule into account too. That is, "In Progress" time of an issue opened on Friday at 5 PM and closed on Monday at 9 AM, will be a few hours rather than 3 days. It has various other reports like assignee time, status entry dates, average/sum reports by any field(e.g. average in progress time by project, average cycle time by issue creation month). And all these are available as gadgets on the dashboard too.

Here is the online demo link, you can see it in action and try without installing the app.

If you are looking for a free solution, you can try the limited version Status Time Free. Hope it helps.

[Rahul_RVS]

Hi @Christopher Marsh 

You can have a look at our app to get this data.

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 grouping
• Save your reports
• CSV Export
• Multiple chart types
• Dashboard Gadget

 

[Jack Brickey]

Natively Jira does not provide a solution for time in status. Their are addon in the Marketplace for this you can consider.

[Christopher Marsh]

Thanks a lot Jack.