Community Announcements have moved! To stay up to date, please join the new Community Announcements group today. Learn more
×Sure, delays suck. But what really wears people down isn’t the waiting it’s not knowing why they’re waiting, or what’s being done about it. Most teams aren’t lazy, they’re just stuck in reactive mode, too busy putting out fires to fix the leaky roof.
But what if you could flip the script?
Imagine knowing where bottlenecks will hit before they slow you down. Or spotting the silent status where tickets go to die. Or using your Jira data not just to explain what went wrong, but to predict what’s about to.
That’s exactly what Time Metrics Tracker | Time Between Statuses, helps you predict. It’s your sidekick for turning raw Jira timelines into clear, actionable insights.
In this article, we’ll break down how to:
Track key time metrics like Cycle Time, Blocked Time, and Time in Status, so you actually know where time goes.
Zoom in with filters by Assignee and Status to see who’s stuck and where.
Forecast risks and delays before they snowball into bigger problems.
Trade firefighting for flow, using data to steer your delivery process.
Build dashboards execs love, using gadgets that spotlight what matters.
So let’s dig in.
Let’s start with definitions. Most teams track “issue done” or “closed,” but time metrics go deeper, telling you how long issues spend in each stage where things get stuck, delayed, or passed inefficiently.
Here are the core metrics our customers usually track in Time Metrics Tracker:
Metric | What It Shows | Why It Matters |
---|---|---|
Time in Status | Time an issue spends in a specific status | Spot where tickets slow down |
Time Between Statuses | Time between defined transitions (e.g., In Progress → In Review) | Reveal handoff and review delays |
Cycle Time | Time from "In Progress" to "Done" | Understand development speed |
Lead Time | Time from ticket creation to delivery | Gauge the end-to-end customer wait |
Time in Progress | Time issue is actively worked on | Monitor team workload accuracy |
Blocked Time | Time spent in a blocked state (e.g., "Waiting for Approval") | Identify critical blockers |
Resolution Time | Time until issue is resolved | Analyze support responsiveness |
These aren’t reports - they’re early warning systems.
Being proactive means you can detect issues before they become problems. This is how top-performing Agile, DevOps, and support teams operate.
Instead of:
"Why is this sprint blocked again?"
"We missed another SLA, why didn’t we know sooner?"
You start asking:
“Which issues have been stuck in ‘Waiting for Review’ for more than 2 days?”
“Which assignee has multiple overdue tasks based on Time in Status?”
“Which projects are trending toward SLA breaches?”
With Time Metrics Tracker’s new gadget filters, this level of insight is now just a click away.
Our latest update introduces two powerful new filters for gadget configuration:
Now you can filter your gadget reports by specific team members - so you can:
Visualize workload imbalances
Track Cycle Time or Time in Status per person
Identify performance patterns or mentoring needs
🧠 Use case: Spot which developers are getting stuck in “Waiting for Review” or “In Progress” too long.
Slice metrics based on only the statuses that matter to you:
Focus on “Blocked” and “On Hold” stages to isolate delay zones
Exclude irrelevant statuses like “Waiting for Deployment”
Customize reports by workflow type or team structure
🧠 Use case: In a shared service team, track only customer-facing statuses to measure true response time.
Time Metrics Tracker includes out-of-the-box gadgets that turn Jira dashboards into control centers:
Gadget | Use For |
---|---|
Time in Status Gadget | Monitor active tickets by time in current status |
Average Time Gadget | Compare performance across projects or teams |
Time Between Statuses Gadget | Track handoff speed and review delays |
Cycle Time Histogram Gadget | Visualize flow efficiency over time |
Status Entrance Date Gadget | Track when items entered key stages |
All gadgets now support:
📌 JQL-based filtering
📌 Time range selection
📌 Assignee and Status filters (new!)
📌 Export to CSV/Excel
📌 Working calendars (no weekends/holidays)
💡Tip: Use a dashboard with “Time in Status” + “Average Time” + “Assignee Filter” to run weekly retros with real, actionable insights.
Use Time Between Statuses with thresholds to:
Trigger alerts for tickets nearing breach
Visualize status duration across teams
Prove SLA compliance with exported audit logs
📈 Organizations using time-based reports reduce SLA breaches by up to 35%, according to Atlassian customer studies.
By tracking Cycle Time over sprints, you can:
Spot delivery slowdowns before release planning
Drill down into specific teams or epic types
Set and monitor improvement benchmarks
🔍 Research: Accelerate: State of DevOps Report confirms that shorter cycle times correlate with higher delivery performance and lower failure rates.
Time Metrics are perfect for teams using OKRs or KPIs like:
“Reduce Cycle Time by 20% this quarter”
“Keep Blocked Time under 10% of total”
“Limit average Time in Review to under 1 day”
🧠 Use historical gadgets to baseline performance and show progress visually.
Being proactive with time metrics lets you:
Deliver on time, with fewer surprises
Forecast risk, workload, and capacity accurately
Justify decisions with real data
Boost transparency and accountability
Build a performance culture, not a blame culture
Install Time Metrics Tracker
Create your first gadget – choose the metric, timeframe, and filters
Add to a Jira dashboard and share with your team
Start spotting trends before they become blockers
👉 Get Time Metrics Tracker on Atlassian Marketplace
Delays will always exist - but blind spots don’t have to. With Time Metrics Tracker, you transform Jira from a static backlog into a real-time performance engine.
By using proactive metrics, smarter filters, and visual gadgets, your team can move from chasing deadlines to mastering delivery.
If you're ready to future-proof your workflows, start with time.
Valeriia_Havrylenko_SaaSJet
Product Marketer
SaaSJet
42 accepted answers
0 comments