Time in status is how long a Jira work item spends in each workflow status, for example, 3 days in In Progress and 6 hours in Code Review. It’s one of the simplest ways to spot bottlenecks and see where delays occur.
Jira keeps every status change in the work item history, but getting the time per status out of it isn’t obvious. Some built-in tools help with quick checks, and some questions need a dedicated marketplace app. Below are both options for tracking it, and how to use time in status reports to analyze your workflow.
Why Jira time in status matters for your workflow
Jira time in status may look like just another number, but it shows what other metrics don’t: where exactly work waits. Here’s why teams track it:
- Spot bottlenecks fast: See which statuses hold work the longest, whether it’s code review, testing, or waiting for approval.
- Base decisions on data: Instead of guessing why a sprint slipped, see how many hours each work item actually spent in each status.
- Balance the workload: If work piles up in one status or with one team, you can reassign work items or change priorities before deadlines slip.
- Fix the right stage: When you know whether delays come from development, review, or handoffs, you can improve that stage instead of the whole process.
How to track time in status in Jira natively
A few built-in options let you see the time spent in status, but with some limits.
| What it shows | Limits |
|---|
Days in column | Dots on board cards showing how long a work item has been in its current column. Enable it in board view settings. | Whole days only, includes weekends, and you need to hover to see the exact number. |
Project and team overview | Average cycle and lead time as widgets on the default Reports page. | Averages only, Jira’s own definition of cycle time, no breakdown by status. |
Control Chart | Cycle or lead time for selected columns in company-managed spaces. | Merges columns into one value, one board at a time, ignores non-working hours. |
Average time in status gadget | Status averages over time on a dashboard. | Resolved work items only, no time per work item. |
JQL | Work items that have been in a status for at least N days. | Can’t calculate or sort by duration. |
There are also more complex options. Automation can save time in a status to a custom field, though each status needs its own two rules and a custom field. With the REST API, a developer can pull the full status history and calculate the rest.
These tools are great for quick checks. When you need time in every status for each work item, across teams, in working hours, that’s where marketplace apps help.
How to calculate time in status in Jira with a Marketplace app
Time in Status for Jira by SaaSJet uses Jira history to calculate how long work items have spent in each status and brings the results into a report. You choose the work items by project, sprint, filter, or JQL, then pick the report that matches your question.
Pick the report for your question
- Time in Status: How long did each work item spend in each status?
- Average Time: How has the average time in each status changed by day, week, month, or quarter?
- Time in Assignee: How long did each person or team work on each item?
- Status Count: How many times did a work item return to the same status?
- Transition Count: How many times did it move between statuses?
- Status Entrance Date: When did a work item first enter each status?
- Time in Status per Date: How much time was spent in each status on each date?
Set it up to match how your team works
- Work schedule. Add your team’s working hours, breaks, holidays, and time zones, so reports count working time, not nights and weekends.
- Status Groups. Combine statuses to get cycle time or lead time.
- User Groups. In Time in Assignee, combine people into groups such as Dev team or QA team to see time per team, not just per person.
Find what slows work down
Sort any time column to bring the slowest work items to the top. You can also filter by a target, for example Testing > 2d, to see only the items above it. Row Grouping compares results by project, sprint, or team using the median, so a few long-running work items don’t skew the numbers. Report Summary shows totals, averages, and work item counts per status in one panel.
Compare groups with Pivot mode
Sorting and filtering show which work items are slow. Pivot mode shows which types of work are slow, and in which status. For example, do bugs wait longer in Code Review than stories? Does one project spend twice as long in Testing as another?
Pivot mode turns the Time in Status report into a pivot table. Put fields such as work type, project, or assignee into rows, statuses into columns, and time into values. Then choose how to calculate them: sum, average, median, min, or max. The median shows the typical time, so a few long-running work items don’t skew the picture.
The pivot keeps your report’s filters and work schedule, and exports to CSV or XLSX exactly as it appears on screen.
See it on a chart
Every report can be switched to a chart and added to a Jira dashboard as a gadget, using the same filters and work schedule as the table.
To chart just part of the data, use integrated charts. Select cells in the table, right-click, and choose Chart range, or build a chart from scratch in the Charts tab. Pick from eight chart types, from stacked columns and histograms to scatter plots, and combine rows by assignee, status, or any other column.
Integrated charts are live: they update when you change the report period or work schedule. To keep the numbers from a specific moment, for example, the end of a sprint, freeze a chart as a snapshot. Charts are saved with the report, and in Pivot mode a chart follows your pivot table.
Take the data further
Export any report to CSV or XLSX, or pull it into Google Sheets, Power BI, or your own tools through the Time in Status API.
Jira time in status custom field: see status time on cards and in JQL
With Time in Status custom fields, status time becomes a regular Jira field. Each field measures either time in the current status to spot work that’s stuck, or a group of statuses, such as Cycle Time or Lead Time. Link a work schedule to count only working hours.
A Jira admin creates the field in the app’s Custom fields settings, chooses where it applies and how often it updates. You can then see the value in the work item view and use it in JQL, filters, and boards.
To show it on board cards:
- On your board, click the three dots and select Board settings.
- Open the Card layout tab.
- In Field name, choose your time in status field.
- Click Add.
Now status time is visible right on the board, without opening a report.
See time in status inside a work item
To check a single work item without opening a report, open it and select Time in Status in the Activity section. You’ll see how long it spent in each status, who worked on it and for how long, and how many times it moved between statuses, as a chart and as numbers. Choose a work schedule to count only working hours.
Now status time is visible on the board and inside each work item, without opening a report.
Time in status on your Jira dashboard
You can also keep time in status data on a Jira dashboard with three gadgets:
- Accurate Time in Status shows any of the seven reports as a table or chart, for example, average time in status per sprint, with your Status Groups and work schedule applied.
- Burndown Status Tracker shows how many work items are in each status over time, so you can see where work piles up. Hover over a value to open the work items behind it.
- Forecast by Time in Status shows how long work items are expected to take in statuses, based on similar completed work, next to the time they’ve already spent, so you can spot items running late.
Real-world use cases for the Time in Status app
Time in Status helps teams understand where work slows down and which workflow stages need attention. Here are a few ways to use Jira time in status reports across departments:
- Engineering & Product: Measure cycle time and lead time, find work items waiting in review or testing, and use Status Count or Transition Count to spot rework.
- Support & ITSM: Analyze time spent in triage, investigation, and waiting for a customer response to understand which stages contribute most to resolution time.
- HR & People Ops: Track how long onboarding tasks and internal requests spend at each stage, and use Time in Assignee to investigate handoff delays.
- PMO & Business Operations: Use Pivot mode to compare time in status across projects or work types, then export the results to CSV or XLSX for further analysis.
For example, if work items spend more time waiting for review than in development, the team can investigate review capacity and handoffs before changing the development process.
Takeaway
Jira already records every status change. Built-in tools are enough for a quick check, but when you need time in every status for each work item, counted in working hours and compared across teams, a time in status report gives you the full picture.
A good place to start is with one question: where did work wait the longest in your last sprint?
🚀 Try Time in Status free for 30 days:
![Photo of Yuliia_Borivets_[SaaSJet]](https://us.v-cdn.net/6038660/uploads/avatars/d0/04/nd004fec77ef393e054b072c4fa545101.png)
