Tracking time-in-status per individual work item — best approach in Jira Cloud? What I'm trying to achieve I want to see, for every ticket, how long it spent in each status from creation through to Done — available both on the issue view and as an aggregated report across the project. What I've tried * Quick filter to hide old Done items from the board — works as a filter toggle but doesn't auto-hide. * Board sub-filter — the new Jira experience doesn't expose a separate sub-filter field. Only a single main filter query is editable, which changes what all users see. * Main board filter with JQL — using status CHANGED TO Done AFTER -3d OR status != Done to auto-drop Done items after 3 days. This works, but it's a board-level workaround, not actual time-in-status tracking. * Automation rule to populate a custom "Days in Current Status" field — scheduled flow using {{now.diff(issue.statusCategoryChangedDate).days}} plus a transition rule to reset to 0. This gives time in current status only, not a historical breakdown per status. * Native reports — Control Chart gives aggregate cycle time, not per-ticket. Issue History tab shows transitions with timestamps but no computed durations. What's missing from native Jira Cloud * No built-in field or panel on the issue view showing "time spent in each status" * No native report showing per-ticket time-in-status breakdown * Custom fields populated by automation can only track current status duration, not historical per-status totals * Card layout on boards only supports native fields, so even a custom field isn't easily surfaced on the card face without workarounds My questions * Is there a way to natively display per-status historical durations on an issue without a Marketplace app? * For those using Marketplace apps (Time in Status by SaaSJet, Status Time Reports by OBSS, etc.), which is most reliable on Standard plan? * Is there a recommended way to expose app-calculated time-in-status values back onto board cards? * Are there plans from Atlassian to add this natively? It feels like a fundamental gap given how often teams ask for it.

Hi @Harry Foreman If you are willing to try an Atlassian Marketplace app, check out eazyBI for Jira Cloud. eazyBI is a reporting and analytics add-on that lets you build variaty of reports, including what you're describing - time-in-status tracking Here's what eazyBI offers for time-in-status reporting * Days in transition status - shows how long each issue spent in a specific status. You can use the Transition Status dimension to filter by one or more statuses and see the duration per issue or as an average across issues. * Average days in transition status - calculates the average time issues spent in a selected status, great for cycle time analysis. * Workdays in transition status - same as above but counts only business days. * Issue cycles — if you want to group multiple statuses together (e.g., "In Progress" + "Code Review"), you can define custom issue cycles and get precalculated metrics like "Average days". On top of this, you can find how much time a ticket has spent in a particular status while being assigned to a specific user. Or while the issue has been flagged or even pair with other single select custom fields for which we can import the change history. The reports can be added as gadgets to your Jira dashboard, and you can filter by project, board, issue type, and more. You can also export sample report definitions and import them directly into your account to get started quickly. Disclosure: I work for the eazyBI team. Best, Elita from support@eazybi.com

Hi @Harry , You've done a thorough job documenting the gap. To confirm your findings: there is no native Jira Cloud feature that computes and displays historical per-status durations on individual issues. So a Marketplace app is the way to go here. As others have already mentioned a few options, I'll add one more to consider. If you're open to solutions from the Atlassian Marketplace, you may want to have a look at JXL. JXL is a spreadsheet/table view for your Jira data with a set of built-in history columns, including:* Time in [status] — how long each issue spent in any given status, computed from the full changelog * Time between [status A] and [status B] — elapsed time between two workflow steps * Time since creation — running issue age These columns support configurable occurrence modes (first, last, all, median, average) and work calendars so you can exclude weekends and holidays. You can sort, filter, and group by these columns just like any other field, and use sum-ups to see averages or totals across groups (e.g. average time in "In Review" per assignee). Disclosure: I work for the team that builds JXL. Hope this helps,Martin

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Individual work item time in status trackingTracking time-in-status per individual work item — best

Harry Foreman_b94pbt

Tracking time-in-status per individual work item — best approach in Jira Cloud?

What I'm trying to achieve

I want to see, for every ticket, how long it spent in each status from creation through to Done — available both on the issue view and as an aggregated report across the project.

What I've tried

Quick filter to hide old Done items from the board — works as a filter toggle but doesn't auto-hide.
Board sub-filter — the new Jira experience doesn't expose a separate sub-filter field. Only a single main filter query is editable, which changes what all users see.
Main board filter with JQL — using status CHANGED TO Done AFTER -3d OR status != Done to auto-drop Done items after 3 days. This works, but it's a board-level workaround, not actual time-in-status tracking.
Automation rule to populate a custom "Days in Current Status" field — scheduled flow using {{now.diff(issue.statusCategoryChangedDate).days}} plus a transition rule to reset to 0. This gives time in current status only, not a historical breakdown per status.
Native reports — Control Chart gives aggregate cycle time, not per-ticket. Issue History tab shows transitions with timestamps but no computed durations.

What's missing from native Jira Cloud

No built-in field or panel on the issue view showing "time spent in each status"
No native report showing per-ticket time-in-status breakdown
Custom fields populated by automation can only track current status duration, not historical per-status totals
Card layout on boards only supports native fields, so even a custom field isn't easily surfaced on the card face without workarounds

My questions

Is there a way to natively display per-status historical durations on an issue without a Marketplace app?
For those using Marketplace apps (Time in Status by SaaSJet, Status Time Reports by OBSS, etc.), which is most reliable on Standard plan?
Is there a recommended way to expose app-calculated time-in-status values back onto board cards?
Are there plans from Atlassian to add this natively? It feels like a fundamental gap given how often teams ask for it.

Accepted answers

All comments

Marc Koppelaar

Hi @Harry Foreman

You need a 3rd party app for this.

I don't use them, so on reliability I can't tell.

What I can give you is:

Try them all and see which is the best fit
Look at security on the apps
Look at Data residency, if this is important

Is there a recommended way to expose app-calculated time-in-status values back onto board cards? -> Not ootb, maybe possible with one of the apps, but II don't think so. Also on a kanban board you can show how long an item is in a column by dots and their colour
Are there plans from Atlassian to add this natively? It feels like a fundamental gap given how often teams ask for it. -> No, not that I have seen and nothing is mentioned in the cloud roadmap

Note in relation to this, based on that Jira is related to agility, time in status measuring in my mind is not related and if this is really important, the Team Lead, Scrum Master or Product Owner should be the one to decide what to do with long time open issues.

A regular "backlog grooming" session should also help in this.

To keep a focussed backlog on what to deliver.

Rahul_RVS

Hi @Harry Foreman

As suggested by Marc, you will need a mktplace app for these requirements. If you would like to try out one, pls explore

Time in Status Reports

With this app you generate time in each workflow status for multiple issues with multiple filter and grouping options. It works for current issues and closed ones as well.

With Status grouping feature, can help you define your own cycle time / issue age time and view the averages of the same. Also the app has 20+ reports to meet a variety of use cases.

You can set your own working calendar to exclude weekends and holidays from the time in status calculation.

More details here.

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

TIS - Avg Time in Status.PNG

Khrystyna_Dzhus_SaaSJet_

Hi @Harry Foreman

You’re absolutely right — this is one of the most common gaps in Jira. There’s no native way to track time in status per issue. Jira focuses more on workflow tracking than time analytics.

So if you need to measure how long an issue actually spends in each status, you’ll need a Marketplace app.

For example, the Time in Status app by SaaSJet (developed by my team) calculates time in statuses based on the issue changelog, not just the current state.

It covers exactly the use cases you wrote about:

- Shows how long each issue spends in each status

image-20250718-133236 (4).png

- Uses the full history (not just the current status)

- Provides 7 types of reports (tables and charts)

- Allows you to create Time in Status custom fields that can be added to board card layouts

If you have any additional questions, I’ll be happy to help 🙂

Birkan Yildiz _OBSS_

Hey @Harry Foreman
First, welcome to the Community!

To get a reliable, historical per-status breakdown for individual tickets without complex workarounds, the most effective approach is to use a dedicated reporting app. Timepiece - Time in Status for Jira by OBSS is one of the most established and reliable tools in the Atlassian Marketplace for this exact use case.

Here is how it directly answers your needs:

Aggregated Project Reports: You can use the Status Duration Report to instantly generate a clean table listing all your issues. It shows exactly how much time each ticket spent in every single workflow status from creation to Done. Timepiece handles over 1 million issues per report smoothly, proving its enterprise-grade performance.

Note: After installation, you can create any report for past and ongoing issues with Timepiece.

Visibility on the Issue View: Timepiece automatically adds a dedicated Issue View Tab directly inside every Jira ticket. This lets you see the complete time-in-status history and charts for that specific work item without having to leave the page or run a project-wide report.

True Business Time: Instead of relying on a 24/7 clock that skews your data with weekends and nights, you can configure Custom Calendars. This ensures your reports only calculate actual working hours and business days.

Board Cards: Exposing dynamically calculated, historical time-in-status values directly onto the board card face is notoriously difficult in Jira Cloud, because card layouts rely on static custom fields. Instead of building fragile automation rules to constantly update custom fields, I recommend to using Timepiece's Dashboard Gadgets. You can place these highly interactive reports directly on your main Jira dashboard, giving you a centralized, real-time view of issue durations and bottlenecks, entirely bypassing the need to clutter your board.

Timepiece AI Assistant: Not sure how to configure a specific metric? Simply type what you're looking for, and the AI will provide a step-by-step guide along with a preconfigured link to generate it instantly.

Hope this helps. You can visit Timepiece’s Atlassian Marketplace page to learn more. Additionally, this community article outlines the primary features and report types that Timepiece - Time in Status for Jira provides.

Please let me know if you have any further questions.

Disclosure: I am part of the OBSS team, the creators of Timepiece.

Best,
Birkan

Martin Sturm - JXL

Hi @Harry ,

You've done a thorough job documenting the gap. To confirm your findings: there is no native Jira Cloud feature that computes and displays historical per-status durations on individual issues. So a Marketplace app is the way to go here.

As others have already mentioned a few options, I'll add one more to consider. If you're open to solutions from the Atlassian Marketplace, you may want to have a look at JXL.

JXL is a spreadsheet/table view for your Jira data with a set of built-in history columns, including:

Time in [status] — how long each issue spent in any given status, computed from the full changelog
Time between [status A] and [status B] — elapsed time between two workflow steps
Time since creation — running issue age

These columns support configurable occurrence modes (first, last, all, median, average) and work calendars so you can exclude weekends and holidays.

You can sort, filter, and group by these columns just like any other field, and use sum-ups to see averages or totals across groups (e.g. average time in "In Review" per assignee).

Disclosure: I work for the team that builds JXL.

Hope this helps,

Martin

Dmytro Rudenko _ Release Management

Hi @Harry Foreman ,

You've done a thorough job mapping out what's possible natively -- and you're right, Jira Cloud doesn't offer a per-status historical duration breakdown out of the box. The automation approach you built for "Days in Current Status" is about as far as native tools go.

Since others in this thread have already covered dedicated time-in-status reporting tools well, I'll offer a slightly different angle.

Time-in-status data is useful, but teams quickly hit the next question: "This ticket sat in Code Review for 5 days -- is that actually a problem, and what should I do about it?" Raw durations need context to become actionable.

That's the gap we built Work Item Health | Scores, Time in Status & AI Insights to fill. It gives you the time-in-status breakdown you're asking about, but adds health scoring and AI-powered insights on top -- so instead of scanning duration tables, you see which tickets need attention and why.

For your specific questions:

Per-issue time in status. Full historical breakdown by status category and individual status, with time bars and return counts, visible directly on the issue. No need to run a separate report.

Health score. Each work item gets an overall A-to-D grade based on lead time, cycle time, efficiency, blocked time, returns, and reassignments. A ticket that's been bouncing between statuses will surface immediately as a C or D without you having to dig.

AI Insights. One click from the issue panel. Surfaces patterns and flags risks specific to that ticket.

The whole thing lives as a panel on the issue view — no separate app window to open, no context-switching.

Here's what it looks like inside a real ticket:

You can try it here: Work Item Health on Atlassian Marketplace

Disclosure: I work at Y2 Release Management Apps, the team that built this app.

Elita Kalāne - eazyBI Support

Hi @Harry Foreman

If you are willing to try an Atlassian Marketplace app, check out eazyBI for Jira Cloud.

eazyBI is a reporting and analytics add-on that lets you build variaty of reports, including what you're describing - time-in-status tracking

Here's what eazyBI offers for time-in-status reporting

Days in transition status - shows how long each issue spent in a specific status. You can use the Transition Status dimension to filter by one or more statuses and see the duration per issue or as an average across issues.
Average days in transition status - calculates the average time issues spent in a selected status, great for cycle time analysis.
Workdays in transition status - same as above but counts only business days.
Issue cycles — if you want to group multiple statuses together (e.g., "In Progress" + "Code Review"), you can define custom issue cycles and get precalculated metrics like "Average <cycle> days".

On top of this, you can find how much time a ticket has spent in a particular status while being assigned to a specific user. Or while the issue has been flagged or even pair with other single select custom fields for which we can import the change history.

The reports can be added as gadgets to your Jira dashboard, and you can filter by project, board, issue type, and more. You can also export sample report definitions and import them directly into your account to get started quickly.

Disclosure: I work for the eazyBI team.

Best,

Elita from support@eazybi.com

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud