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

[Harry Foreman]

---

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

1. Quick filter to hide old Done items from the board — works as a filter toggle but doesn't auto-hide.
2. 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.
3. 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.
4. 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.
5. 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

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

[Marc -Devoteam-]

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:

1. Try them all and see which is the best fit
2. Look at security on the apps
3. 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