Time in status is the most direct way to find bottlenecks in your Jira workflow. Instead of guessing where work slows down, it shows exactly how long issues sit in each status — status by status, period by period — so you can see the queue that is stretching your delivery. This guide explains what time in status is, how Flow Metrics Charts for Jira Cloud measures it, and how to use it to cut cycle time.

What is time in status?

Time in status measures how long issues spend in each workflow status — To Do, In Progress, In Review, Test, and so on. It turns your workflow into a map of where time is actually spent, exposing the queues and handoffs that quietly stretch delivery. Where cycle time tells you the total active duration, time in status tells you where that duration went.

Two ways to view it

• Average — the average number of days an issue spends in each status. Ideal for spotting which single stage consumes the most time.
• Ratio — the percentage of total time spent in each status. Perfect for seeing the shape of your process at a glance and comparing periods fairly, regardless of volume.

How time in status is measured in Jira

Flow Metrics Charts reconstructs each issue’s journey from its changelog and aggregates the time spent in every status across your chosen project, board, saved filter or JQL. Results are shown per period in days, so you can watch how a status — say, code review — trends over time rather than reading a single snapshot.

How to read the chart

• The status that swells over time is your constraint. That is where process changes pay off most.
• Separate waiting from working. Long stretches in “waiting” statuses (Ready for Review, Blocked) point to queue and handoff problems, not effort problems.
• Compare the Average and Ratio views. A stage can be small in absolute days but a growing share of the whole — an early warning worth catching.

Why time in status matters for your business

Most delivery delay is waiting, not working — and time in status is what makes that waiting visible. It locates bottlenecks precisely so you stop optimising the wrong stage, it validates improvements (after a change, the time in the targeted status should fall), and it supports SLAs, letting service teams monitor time in customer-facing statuses to protect response and resolution targets.

How to use time in status to cut cycle time

• Attack the biggest bar first. The status with the most time is your constraint; removing its handoff or approval delivers the largest cycle-time gain.
• Reduce queues, not just work. Adding a reviewer or a WIP limit on a waiting stage often beats asking people to work faster.
• Re-measure after each change to confirm the time actually moved, rather than shifting the bottleneck downstream.

How time in status connects to the other flow metrics

Time in status is the diagnostic layer beneath the headline metrics. The waiting it exposes is exactly the gap between cycle time and lead time, and reducing it lowers both. Paired with work in progress, it shows not just how overloaded you are but exactly where the overload piles up.

Track time in status in Jira

Flow Metrics Charts for Jira Cloud calculates time in status directly from your Jira changelog — no manual timers — on an interactive board and in dashboard gadgets, with Rovo AI reading the chart and naming the bottleneck for you. Start with the flow metrics for Jira overview, or read the Flow Metrics Explained guide.

Frequently asked questions

What is time in status in Jira?

Time in status is how long issues spend in each workflow status, reconstructed from the issue changelog. It reveals where work waits, making bottlenecks easy to find.

What is the difference between the Average and Ratio views?

Average shows the mean days per status — best for finding the single slowest stage. Ratio shows the percentage of total time per status — best for comparing the shape of your process across periods.

How do I find bottlenecks with time in status?

Look for the status that consumes the most time or whose share is growing. That stage is your constraint; removing its handoff, approval or queue delivers the biggest reduction in cycle time.

Rob Borges

Rob Borges spent the first half of his career hunting waste as a Lean Six Sigma Master Black Belt and wrangling portfolios as a PMI Portfolio Manager — until he realized the tidiest process on earth still can't out-plan an optimistic human. So he switched sides and became an Agile Coach. These days he helps Kanban, Scrum, and Agile-at-Scale teams trade gut-feel deadlines for flow data, turning "we'll probably ship sometime in Q3" into release dates leaders can actually take to the board. His rule of thumb: hope is not a forecast, but your throughput history usually is.

See Full Bio