Most project delays don’t look like disasters. No one fails a task instantly or obviously. In fact, everything often happens quietly: a task “hangs” in the In Review status for a week because everyone on the team assumes someone else is working on it. The sprint ends, and the retrospective turns into a meeting where people simply shrug.
The Time in Status metric makes these hidden problems visible. It tracks how long each Jira task actually spends at every stage of the workflow, including all the stops between start and finish. This is exactly the level of detail teams often miss when trying to diagnose delivery issues.
However, raw numbers are not always helpful during stand-ups. A table showing that one task spent 4.3 days in QA and 1.1 days in Code Review takes time to analyze. A Jira Chart Time in Status report visualizes this data instead, making bottlenecks easier to spot at a glance.
Teams using Time in Status app by SaaSJet can view this data directly in Jira as charts and graphs, without exporting data or creating separate formulas in spreadsheets.
What Is Time in Status in Jira?
When a Jira issue changes status, the system automatically records the corresponding timestamp. Time in status is the interval between these timestamps — the actual time an issue spent in In Progress, Waiting for QA, Under Review, or any other status before moving to the next stage.
It sounds simple, but without the right tools, this metric can be quite difficult to track.
Why this metric matters for teams:
- SLA / Service Level Agreement. If you’ve committed to closing support requests within 48 hours, you need to understand where time is being lost in the workflow. Saying “we closed the issue” does not show that it may have spent 36 of those 48 hours sitting idle in the Waiting on Customer status.
- Cycle Time. The difference between a productive team and a slow one often comes down not to how fast people work, but to how long tasks remain inactive between steps. Time in status helps teams clearly distinguish between active work time and passive waiting time.
- Bottleneck Analysis. Every workflow has a weak link. Time in Status shows exactly which stage or task handoff is slowing down your workflow — not as an assumption, but as a concrete number.
Calculating all of this manually means constantly exporting logs, building formulas, and updating tables after every change. Time in Status app by SaaSJet automates this process: it pulls data directly from Jira and visualizes it in charts and dashboards that are easy for the entire team to understand.
Why Visualizing Time in Status Matters for Agile Teams
There is a huge cognitive gap between analyzing data in a spreadsheet and visualizing it in a chart. When we look at raw numbers, our brain has to actively calculate, compare, and search for patterns line by line. Visual charts, on the other hand, make patterns easier to recognize, allowing managers to quickly spot trends, sudden changes, and anomalies.
Moving from raw data to visual time in status charts gives Agile teams several important benefits:
- Instant bottleneck identification: If the QA stage stretches across the chart or takes up a large share of a pie chart, it becomes clear that testing may be overloaded or slowing down delivery.
- Data-driven retrospectives: Instead of relying on intuition to understand sprint issues, teams can use visual evidence to see exactly where work got stuck.
- Transparent stakeholder reporting: Customers and stakeholders rarely want to dig through individual Jira issues. A clear time in status chart makes progress, delays, and workflow obstacles easier to understand.
What is a Jira Time in Status Chart?
Jira Time in Status Chart metric visualizes the total or average time issues spend in each stage of a workflow. It uses historical Jira transition data and displays it through bar charts, pie charts, or other chart types, helping teams quickly identify where work gets stuck the longest.
Introducing Jira Chart Time in Status with SaaSJet
Time in Status by SaaSJet is a Jira app available on the Atlassian Marketplace that automatically tracks how long issues spend in each stage of a workflow.
Instead of manually reviewing issue history or exporting raw Jira data to spreadsheets, teams can visualize time in status directly in Jira. This makes it easier to identify bottlenecks, understand what slows work down, and discuss process efficiency during sprint reviews, retrospectives, or stakeholder reporting.
The app pulls data directly from Jira and presents it in clear, easy-to-understand visual formats that can be shared with teammates, managers, and stakeholders.
With Chart View, teams can visualize time in status data as area, column, pie, or sunburst charts. This helps them quickly compare workflow stages and identify where work takes the longest, such as Review, QA, Approval, or Waiting.
Teams can also use Table View to analyze time in status data in a structured format.
Together, these views help teams move from raw Jira data to clear workflow insights: precise numbers for deeper analysis and visual context for faster communication.
How to Set Up Your Jira Chart Time in Status (Step-by-Step)
Getting started with Time in Status is straightforward. Here’s the basic workflow:
Step 1: Install the app. Find Time in Status by SaaSJet on the Atlassian Marketplace and install it for your Jira Cloud or Data Center instance. A free trial is available.
Step 2: Open your project. Navigate to any Jira project and open the Time in Status app from the project sidebar or apps menu.
Step 3: Set your filters. Click report type, filter the work items (by assignee, project, sprint, etc), set the date ranges, choose work schedule, set time format and configure columns & grouping.
Step 4: Switch to chart view. Click into the chart view to see a visual breakdown of how long issues have spent in each status. The bars are immediately comparable — taller bars mean more time, and outliers stand out instantly.
Step 5: Switch to graphic view. Toggle to the table view for a detailed grid with issues and metrics.
Step 6: Identify outliers. Look for statuses or individual issues that are dramatically out of range. A story that spent three days in “In Progress” and nine days in “Code Review” is telling you something important.
Step 7: Share or export. Share the report with your Scrum Master, engineering manager, or team lead. Use the data in your next retrospective or sprint planning session.
💡 Pro tip: Screenshot the chart view at the end of every sprint and keep a folder of them. After three or four sprints, patterns become impossible to ignore.
→ Try Time in Status by SaaSJet on the Atlassian Marketplace
FAQ
How do I create a time in status chart in Jira?
The easiest way is to install the Time in Status app by SaaSJet from the Atlassian Marketplace. Once installed, you can select your project, apply filters, and view a chart or graphic breakdown of time spent in each status — without any manual data processing.
Can I add a time in status chart to a Jira dashboard?
Yes. With the Time in Status app, you can pin the report as a gadget on your Jira dashboard so your team always has live visibility into workflow status durations.