How to See Workflow Health in Jira Without Exporting Anything
Every team has workflow data in Jira. Status changes, transitions, timestamps — it’s all there.
The problem is turning that data into a useful picture during an actual review. Not after an hour of exporting. Not with a spreadsheet someone built last quarter. But right now, in context, when the question comes up.
That’s the practical problem Flow Insights in Time Metrics Tracker solves.
Step 1: Create the metric that fits your process
Before using Flow Insights, you first create the metric you actually want to measure.
Different teams measure different things:
- A software team might track time from In Progress to Done
- A QA team might care about Review Time or Validation Time separately
- A support team might need Resolution Time, but only when the ticket was actively worked on — not sitting in On Hold
- An operations team might want to track Approval Time or time spent waiting for a third party
In Time Metrics Tracker, you configure each metric to match how your team actually works.
Choose the statuses to measure
Define where the clock starts and where it stops — based on your specific workflow, not a generic definition.
Add your working schedule
If your team works Monday to Friday, 9 to 6, the metric should reflect that. Otherwise, a ticket sitting over the weekend can inflate your numbers.
Exclude statuses that should not count
If On Hold or Waiting for Customer represents time your team does not control, you can exclude it. The metric then measures only the time when work was actively moving.
Set warning and critical limits
Define what “normal” looks like for your team. Anything above the threshold gets flagged visually, without manual checking.
Step 2: Select the metric and open Flow Insights
After the metric is ready, go to the global report page, select the metric, and open Flow Insights.
No exports. No pivot tables. No waiting.
You immediately see KPI summary cards and four connected charts — all based on the metric, project, and date range you selected.
This is the overview layer: a quick read on workflow health before deciding whether a deeper investigation is needed.
What you see in Flow Insights
KPI cards — 30-second triage
Before going into any chart, the summary cards give you a fast read on the current state:
Trend estimate — is the metric improving, worsening, or staying stable compared to the selected period?
Median value — what does a typical completion look like?
P85 value — how long does slower work take? This matters because the median can look fine while a tail of problematic tickets quietly affects predictability and creates delivery risks.
Average share and total tracked time — how the selected metric is distributed across the current context.
After this quick overview, you can open the full Flow Insights view by clicking Open full insights view. There, you’ll see four key charts that help explain what is happening inside your workflow.
Trend chart — is the process moving in the right direction?
The Trend chart shows how the selected metric changes over the chosen period.
The value is not just seeing a number. It’s seeing the direction.
If Cycle Time has been increasing for three consecutive weeks, that is an early signal — not a post-mortem. A delivery manager can bring that insight into a stakeholder conversation before it becomes a missed deadline.
Contribution chart — where does the time actually go?
When a metric looks high, the real question is: which status is responsible?
The Contribution chart breaks down how tracked time is distributed across workflow stages — whether that’s Review, QA, Approval, Waiting for Customer, or any other stage in your process.
Instead of asking, “Why is this metric high?”, the team can ask something more specific:
“Review is consuming 40% of the total time — is that expected, or is there a bottleneck?”
That is a question the team can act on.
Work in Progress chart — is pressure building before it becomes visible?
WIP problems show up in completed work, but they start earlier.
If too much work is active at once, or if blocked work is growing, longer cycle times will usually follow. By the time the completed-work metric reflects it, the damage may already be done.
The WIP chart helps surface that pressure while there is still time to act.
A delivery lead might notice that the median value looks stable, but blocked work has been growing for two weeks. That is a signal to check dependencies and handoffs now — not after the sprint ends.
Scatter Risk Map — isolated delays or a pattern?
Not every slow ticket means the whole workflow is broken.
Sometimes most work moves normally, while a small cluster of issues pulls the numbers up. The Scatter Risk Map shows how work items are distributed — stable completions on one side, risk-clustered outliers on the other.
This helps answer the question that averages cannot:
“Is this a process problem — or are there five specific tickets we should look at right now?”
Step 3: From overview to drill-down
The overview is just the starting point.
Once the KPI cards and charts surface a signal — a worsening trend, a stage consuming most of the time, or a growing risk cluster — you can move from the surface-level view to the specific work items behind it.
The drill-down helps you go from:
“Cycle Time increased this week”
→ “The Contribution chart shows Review is the main factor”
→ “The Scatter Risk Map shows six tickets in the risk cluster”
→ “Here are those six tickets — let’s look at what happened”
That is the full analysis path, without leaving Jira or touching a spreadsheet.
Why this matters in practice
Most teams already try to answer these questions. They export Jira data, build spreadsheets, compare periods manually, and dig through individual issues.
That approach works, but it takes time. It can also become inconsistent: different people may pull different numbers, use different filters, or rebuild the same report every week.
Flow Insights is designed to make the first layer of this analysis fast and repeatable.
The overview takes minutes, not hours. And because the metric is configured once to reflect your actual workflow, the same analysis is available to everyone on the team — every week, without rebuilding anything.
A practical example
A support team wants to review Resolution Time, but only count the time when tickets were actively worked on — not the time spent waiting for a customer.
Here’s the workflow:
- Create a Resolution Time metric
- Exclude Waiting for Customer from the count
- Apply the team’s working hours, for example Monday to Friday during business hours
- Set a warning limit at 5 days and a critical limit at 10 days
- Select the metric in the report and open Flow Insights
In one view, the team can immediately see:
- Whether Resolution Time is trending up or down this month
- Which stage — Triage, Investigation, or Escalation — contributes most to the total time
- Whether active or blocked ticket volume is building pressure
- Whether delays are spread across all tickets or concentrated in a few accounts
Then, if the Scatter Risk Map shows a risk cluster, the team can drill down into those specific tickets and understand what is actually happening.
The point
Your Jira already contains the workflow history.
Flow Insights helps you read that history clearly — without exports, without manual work, and without waiting until after something goes wrong.
If you want to try it on your own data, Time Metrics Tracker is available on the Atlassian Marketplace with a free trial.
Together, these cards answer one question first: should we look deeper, or does the workflow look healthy right now?
Was this helpful?
Thanks!
Anastasiia Maliei SaaSJet
0 comments