How can I get the time that an issue spend/stay on each status?

[caof]

Just wanted to know if there is some report/JQL that can provide the time that an issue spend an each status ?

Or if not how can I build something that can give me that info?

[Yuliia_Borivets__SaaSJet_]

Hi @caof 

 To get the time that an issue spent in each status, consider these options:

• Built-in Jira feature Days in Column (available only for classic boards). You’ll get only the number of days an issue has stayed in the column. You can learn how to enable this feature here. But if you instead need to remember time measurement over time, by status (e.g., how long was I in status <X>), you would need to explore other options.
• Use custom fields and automation rules to measure the time in status.
• Check the Atlassian Marketplace add-ons. Time in Status for Jira Cloud is developed by my team to get the time the employees spent in each status automatically.

Hope you find the best solution for you.

[Mehmet A _Bloompeak_]

Hi @caof ,

It is not possible using the built-in JQL functionalities of Jira. We developed Status Time app for this exact need. It provides reports on how much time passed in each status, status entry dates and status count.

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(eg. 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.

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

[amitajmera777]

Hi @caof , 

"If you're trying to figure out how long issues stay in each status, it can be tricky in native Jira. I had the same challenge and built a small app called Workflow Aging that gives this visibility — might help you spot bottlenecks quickly."

[Ilze Leite-Apine - eazyBI]

Hi @[deleted] 

As mentioned in previous comments, some Marketplace Jira app would do this. If you are interested to dig deeper in reporting, you may consider checking eazyBI for Jira app where building reports on issue change history is an out-of-the-box option.

There is a report from the eazyBI Demo account with information about days spent in the selected status for each issue: Issue days in status.

The report shows how long each issue has spent in the select status (In Progress, in this report) regardless if the issue has left the status ("Days in transition status" measure) or still is in this status ("Days in transition status till now").

This information also can be analyzed not on issue level, but, for instance, to get the average time spent in each status per project, issue type, time period, etc. which can be used to analyze cycle time: Average time in status (cycle time).

Feel free to contact support@eazybi.com for any further questions!

Ilze, eazyBI Customer Support Consultant

[Emre Toptancı _OBSS_]

Hello @caof

The needed data is available in each issue's history but Jira does not give this as a ready-to-use report.

You can try to measure this using some automation rules. You will find many samples in many answers in this community. The downside is it is not easy to configure and maintain. It also works only for future issues.

You can use the Control Chart of Kanban Boards or the Average Age gadget. Those are good to give you an overall picture but have low flexibility. And they don't show individual issues.

You can try getting the data via REST and doing your own calculations. That requires serious code development.

Finally, you can try using an existing app from the marketplace.

Our team at OBSS built Timepiece - Time in Status for Jira app for this exact need and 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 assigned to each assignee. You can also combine statuses into consolidated columns to see metrics like Ticket Age, Cycle Time, or Lead Time. 

You can calculate averages and sums of those durations grouped by the issue fields you select. 

  

 

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.

The app has custom calendar support. For each report type, you can define your own calendars with your own working days, working hours, holidays, and timezone.

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

[Mayur Jadhav]

Hi @caof 

You have Gadgets with give you a little insight on that information. In your dashboard you can add the following gadgets:

[Mayur Jadhav]

you would be interested in a ready made solution, You may want to try out the plugin, Agile Tools : Epic Tree & Time in Status 

It provides 3 major functionalities in one add-on

More than 7 types of Time in 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 reports

Epic Hierarchy / Sum Up (Standard Jira Hierarchy Epic -> Story -> SubTask)

Link Hierarchy / Sum Up (Hierarchy based on your issue link, upto 10 level deep)

If it works for you then please accept the Answer😊

Thanks,

Mayur