How to see time in status in Jira

“How long has this been In Review?” is a question Jira’s issue view can’t answer at a glance. To see time in status: open the issue’s History tab, note the timestamp of each status change, and subtract — the gap since the last transition is how long it’s been in the current status, and summing the gaps between every pair of transitions gives you each status’s total duration. Jira records all of this in the changelog; it just never adds it up for you, so beyond one issue you’re either doing that subtraction by hand or using an app that does it automatically. Here’s how, per status, so a stalled stage stops hiding in the history.

What Jira shows natively

On any issue, Jira gives you the current status and a History tab that logs every status change with a timestamp. What it doesn’t give you:

• A per-status duration. There’s no “3 days in To Do, 6 days in In Review” breakdown — you’d reconstruct it by reading transitions and doing the subtraction yourself.
• A view across issues. Even if you work it out for one issue, there’s no board or project view that shows time in status for all of them, so you can’t see which stage is slow overall.

So the data is all there in the changelog; it’s just never added up for you.

How to see it per status

• Read it off the history for one issue — note each status-change timestamp and subtract. The gap since the last transition is how long it’s been in the current status.
• Decide whether calendar or working time matters. An issue that sat over a weekend didn’t take two extra days of effort — for a fair figure you’ll eventually want weekends and holidays skipped.
• Compare the same status across issues to find the bottleneck. The single end-to-end number hides where time goes; the per-status view points straight at it — see how to find bottlenecks in Jira.

Without reading the changelog by hand

Linger computes this from the changelog in your tenant and shows how long the issue has spent in each status, right on the issue — free, no JQL, nothing to configure. Its Standard tier adds cross-project reporting and counts time in real working hours. For the end-to-end figure built on top of this, see how to measure cycle time in Jira; for how it differs from Jira’s native chart, see control chart vs time in status.

The takeaway

Jira records every status change but never totals the time per status, so “how long has this been In Review?” turns into changelog archaeology. Read the transitions for one issue, or surface time in status on the issue itself and compare across your work — then the stage where work stalls becomes something you can see instead of guess. If you’d rather not build it by hand, compare the dedicated time-in-status apps for Jira.