Metric: Time in status

Applies to

Time in status measures how long an issue stays in a specific status - for example, how many hours or days it remained in In Progress, Code Review, or Testing.

Use the Time in status metric to identify bottlenecks by seeing where issues spend the most time or to track the efficiency of specific workflow stages (e.g., QA).

On the Time in status chart, the metric is displayed as:

Aggregated or average values (depending on the selected view) - on the chart (1️⃣) and in the Breakdown (2️⃣).
Individual values for each work item in the Issue list (3️⃣).

By default, the chart calculates time in status for all statuses in the In Progress category, but you can select custom statuses if needed.

How time in status is calculated

The chart counts the time between when an issue enters and leaves a status. If the issue moves to the same status multiple times, all durations are added together.

The calculation respects your work schedule - only working hours are counted. For example, if your schedule defines 8-hour workdays and 5-day weeks, 2 days = 16 hours (not 24) and 2 weeks = 10 days = 80 hours.

Statistics calculation (for the Average view)

Per-status calculation: For each status, the chart calculates how long each issue spent in that status, then applies the selected statistical measure (e.g., Mean, Median, 85th percentile) to those values.
Grouped status calculation: The chart sums the time each issue spent in all selected statuses, then applies the statistical measure to these totals. So, depending on the values and statistical measures selected, the group value may or may not be the sum of individual status values.