Time in Status Report and Status Transition report

Time in Status Report and Status Transition report

Category

Time and workload

Category

Time and workload

Description

How long do issues stay in each status, and where is the process stalling?

Overview

The Time in Status report shows how long issues spent in each status of their workflow. It reads the status history of every issue, so it counts every status an issue has been in — not only the current one. Use it to find bottlenecks, measure issue aging and check SLA targets in Agile and ITSM processes.

The same template also covers status transitions: how often issues entered a status, how many times their status changed, and when they first or last moved into or out of a status. See Status transitions.

Default configuration

Setting

Default

Setting

Default

Chart

Pivot table (vertical)

Rows grouping

Project, then Issue

Columns grouping

Changelog Status — every status from the issue history

Cell content

Sum of Time in Status, in hours

Create the report

In Report Builder, open the Templates tab and type Time in in the search field. Click the Time in status template.

Templates tab with the Time in status template

The report opens on the left and the Configure panel on the right. The report is calculated straight away for the current scope.

Select the scope

Expand Get data and click the Scope field. Pick projects, single issues or saved Jira filters, then click Apply filtering. To type a JQL query instead — for example to limit the report to bugs — click Switch to JQL.

Scope selection with the Mobile Dev project

Read the result

Each row is an issue (grouped by project in the default configuration); each column is a status. A cell shows how long that issue spent in that status in total, including repeated visits. The Total column adds up all statuses; the Total row adds up all issues.

Time in status per issue and status, in days

In this example Project was removed from Rows grouping and the values are shown in days.

Customize the report

All fields are in Set chart and fields.

Set chart and fields with the default Time in status fields
  • Rows grouping — what each row is. Group by Issue Type, Assignee or Priority instead of Project to compare groups.

  • Columns grouping — Changelog Status gives one column per status.

  • Cell content — the measure. Click Add cell content to add another one.

Change the time unit

Values are shown in hours by default. Click the arrow on Sum of Time in Status and change Format to second, minute, hour, day (Jira workday duration), day (24h) or pretty (weeks, days, hours and minutes).

Value settings with Format set to day (24h)

Time in status measures

Click Add cell content and search for Status to see all status-related measures.

Add cell content dialog filtered by Status
  • Sum, Average, Median, Min and Max of Time in Status — total or typical time per status.

  • … of Time in Status (24/5) — the same, counting 24 hours a day on working days only (Monday to Friday), so weekends do not inflate SLA times.

  • Time in Assignee (and its 24/5 variant) — how long issues were assigned to each person, based on the assignee history.

Status transitions

To analyse how issues move through the workflow, use these measures instead of — or next to — Time in Status:

  • Count of Status Occurrence — how many times an issue entered each status. Values above 1 show reopened issues or ping-pong between statuses.

  • Count Of Status Changes — how many times the status of an issue changed in total.

  • First / Last Transition To Status Date and First / Last Transition From Status Date — when an issue first or last entered or left a status. Useful for custom SLA checks.

  • Single Issue Status History — the full status history of an issue as text.

Count of Status Occurrence per issue and status

Use cases

  • Find process delays, for example issues that stay too long in In Progress or in review.

  • Measure issue aging by status.

  • Find reopened issues with Count of Status Occurrence.

  • Check SLA targets with the 24/5 measures and the transition dates.

Save the report

Changes to a template are not saved until you click Add to My Reports, which saves the configured report as your own.