Time in status shows where work waits. A ticket that spends one day in progress and four days in review has a review problem, not a coding problem. This guide covers what Jira shows natively, the JQL that helps, how to build a time in status report yourself and what none of these can show.
Jira Cloud now calls projects spaces and issues work items. Jira Data Center keeps the old names. The steps below use the Cloud names.
What Jira shows natively
Days in column on the card
On company-managed boards, Jira can show how long a card has been in its current column as a row of dots (1, 2, 3, 5, 8, 12 and 20 or more days). Open the board, select More actions (•••) > Board settings, then Layout > Card layout and turn on Days in column. It is on by default for Kanban boards and off for Scrum boards. If a work item moves back to a column, the count continues from where it stopped (Atlassian: customize cards).
Days in column answers “how long has this card been here?” for one card at a time. It does not add up time across statuses.
Control chart
The Control chart plots the time each work item spent in the statuses you pick, which makes it the closest native view of cycle time. Open Reports in your space, select More reports if you see space insights first, then Control Chart. Use Refine report to choose the columns: pick only In Progress and In Review to see cycle time, or every column from the first to see lead time. The chart is available for company-managed spaces only (Atlassian: Control chart).
Time in status insight
On company-managed boards, the Insights button shows how long work items stay in each status, for up to five statuses where work takes the longest. It also flags work items that stay longer than the 85th percentile for their status (Atlassian: board insights).
Space insights and work item history
The Reports tab opens space insights, where admins can add metrics such as Average time in current status and Average work item cycle time (Atlassian: insight metrics). Some metrics need the Premium or Enterprise plan (Atlassian: space insights). For a single work item, filter its Activity section by History to see every status change with its date (Atlassian: activity types).
Find work items by status history with JQL
JQL cannot return time spent in a status, but it can find the work items whose status history you want to measure. The WAS and CHANGED operators search past values of the Status field (Atlassian: JQL operators):
status WAS "In Progress"
status WAS "Resolved" BY jsmith DURING ("2010/01/01","2011/01/01")
status CHANGED FROM "In Progress" TO "Open"
status CHANGED FROM "In Progress" TO "Done" DURING ("2026/10/01","2026/10/31")These operators work with status names, not status IDs. If a work item has more than 10,000 changes, WAS searches only the most recent ones. In Jira Cloud you can also find work items whose status category changed recently, for example statusCategoryChangedDate <= -7d (Atlassian: statusCategoryChangedDate).
Build a time in status report from the changelog
Every status change is stored in the work item’s changelog. To get a time in status report for many work items, read the changelogs and add up the time between changes (Atlassian: Jira Cloud REST API, issues):
- Find the work items with JQL, for example everything moved to Done last month.
- Fetch their changelogs with
POST /rest/api/3/changelog/bulkfetch(up to 1,000 work items per request, filtered to thestatusfield) or one by one withGET /rest/api/3/issue/{issueIdOrKey}/changelog. - For each status change, take the
createdtime and thefromStringandtoStringvalues. - Sort the changes by time. The time in a status is the gap between entering it and leaving it; add up repeat visits.
- Group the results by status, work item type or team, and report the median and the 85th percentile, not only the average.
If you would rather not build it, the Atlassian Marketplace lists many apps that add a time in status report to Jira (Marketplace search).
Example: time in status for one bug
An example of what the changelog gives you for a single bug, with the time in each status worked out from the change dates:
| Status | Entered | Left | Days | Share |
|---|---|---|---|---|
| To Do | Oct 6, 09:12 | Oct 7, 14:40 | 1.2 | 15% |
| In Progress | Oct 7, 14:40 | Oct 9, 16:05 | 2.1 | 26% |
| In Review | Oct 9, 16:05 | Oct 13, 11:30 | 3.8 | 48% |
| QA | Oct 13, 11:30 | Oct 14, 10:15 | 0.9 | 11% |
Almost half of this bug’s 8.0 days went to review. Across a month of work items, the same split tells you whether to add reviewers, set a WIP limit on the review column or change who picks up reviews. The cumulative flow diagram guide shows how to spot the same queue on a board.
Which approach to use
| Approach | Good for | Limits |
|---|---|---|
| Days in column | Spotting stuck cards in standups | Current column only, company-managed boards |
| Control chart | Cycle time trends and outliers | Company-managed spaces only, one board at a time |
| Board and space insights | Slowest statuses at a glance | One space, some metrics on Premium and Enterprise |
| Changelog API | A full report across spaces and teams | You build and maintain it |
To see time in status next to your other flow metrics, read how to build a Jira dashboard for flow metrics.
What Jira doesn’t show
Time in status measures how long a work item sat in a status, not what people did in that time. A work item “In Progress” for three days may have had four hours of work, with the rest spent in Slack threads, in a helpdesk ticket, waiting for a build or on other work. Jira cannot see time spent outside Jira or the switching between tools.
hey.space adds that missing part. It imports Jira projects, epics and work items as tasks and matches the team’s activity from TimeCamp’s desktop app to them, so you see active time per work item next to its time in status, and which handoffs are worth automating. See how hey.space finds automation opportunities or the sample report.