How to capture the state transition time for each of the issue status automatically ?

[Amit Mohide]

How to capture the state transition time for each of the issue status automatically ?

I can see the time elapsed in particular status in the "Transitions" tab for each issue. But how can I pull this data automatically for all issues in a project ?

[Iryna Menzheha_SaaSJet]

Hi @Amit Mohide 👋
Welcome to the Community 

Great question — you're right that Jira shows time spent in each status in the Transitions tab per issue, but unfortunately, there's no native way to automatically extract that data across multiple issues or for an entire project.

For automatic and scalable tracking of status transition times, I’d recommend Time in Status

With this app, you can:

• 📊 Use dashboard gadgets to visualize trends

• 🔄 Track status transition times automatically for all issues

• 📁 Export full reports in CSV/Excel

• 🎯 Filter by project, assignee, sprint, date, etc.

• 🧩 Use Sprint Report to get insights about team velocity, workload, carryover, etc.

It works retroactively, so you can analyze historical issues too.

---

Let me know if you’d like a walkthrough or have specific use cases in mind!
Add-on developed by my team. 

[Rahul_RVS]

Hi @Amit Mohide 

Welcome to the community !!

If you would be interested in a mktplace app for this requirement, you can try out

Time in Status Reports 

With this app you generate time in each workflow status for multiple issues with multiple filter and grouping options. The app has 20+ reports to meet a variety of use cases. Pls do reach out for any further queries.

More details here.

Disclaimer : I am part of the app team for this add-on

 

[Ayça Erdem_OBSS_]

Hello @Amit Mohide 

Welcome to the community!

Jira doesn’t offer a built-in way to track how much time each issue spends in different statuses. To get this kind of insight, I recommend using a marketplace app.

Timepiece - Time in Status a, developed by my team at OBSS, is the oldest in the Atlassian Marketplace for this purpose. It's available for both Jira Cloud and Data Center.

Timepiece mainly allows you to see how much time each issue spent on each status or each assignee. 

Status Duration report (please see the screenshot above) which shows how much time each issue spent on each status. You can combine the time for multiple statuses to get metrics 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 or average resolution time per sprint, week, month, issuetype, request type, etc. The ability to group by parts of dates (year, month, week, day, hour) or sprints 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.

Tiimepiece 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. Also you can export the reports in to various formats easily. 

Visit Timepiece - Time in Status for Jira to explore how our JIRA add-on can revolutionize your metrics measurement process.

Hope it helps,

Ayça 

[Melbrin NGOUILOU]

Hi Amit,

Yes, it’s absolutely possible to capture the time spent in each status automatically across all issues in a project — but it’s not available natively in Jira without some scripting or plugins.

Two main options:

1. Use Jira REST API + script

You can use the Jira API to extract each issue’s status history and calculate the time spent in each status programmatically.

2. Use a Marketplace App

Tools like Time in Status or EazyBI can provide this information directly with no code required.

Feel free to ask if you have more questions.