How do you analyze where time is spent in your Jira workflow?

[Anastasiia Maliei SaaSJet]

Hi Community,

I’m curious how different teams analyze where time is actually spent in their Jira workflows.

Many teams track metrics like Cycle Time, Lead Time, Resolution Time, or time in specific statuses such as Code Review, QA, Waiting for Customer, or Blocked. But one challenge I often see is that a single number does not explain the reason behind the delay.

For example, if Cycle Time increased this month, the next questions are usually:

• Which status contributed most to the total time?

• Is the delay caused by a few outlier issues or a wider pattern?

• Is WIP building up in a specific part of the workflow?

• Did the trend get worse gradually or after a specific point?

I’m interested in how teams currently investigate this in Jira.

Do you usually use Jira dashboards, JQL, exports, marketplace apps, custom reports, or spreadsheets?

For context, we recently added a Flow Insights view in Time Metrics Tracker | Time Between Statuses, where teams can select a custom time metric and review related signals in one place: trend, status contribution, WIP, and outliers.

I’d love to hear how you approach this today:

1. What metric do you check first when workflow performance gets worse?

2. Do you care more about trend, status breakdown, WIP, or outlier issues?

3. What would make this type of analysis easier inside Jira?

[Germán Morales _ Hiera]

Hi @Anastasiia, from the admin side the first thing I look at isn't a single number but where the work is actually sitting, time in status, because an aggregate like cycle time tells you it got worse, not where. Status breakdown plus WIP is what points at the bottleneck for me; trend tells me when it started and outliers tell me whether it's a pattern or just a couple of stuck issues, but those come second.

The honest difficulty is that native Jira doesn't give clean time in status. The Control Chart and the Cumulative Flow Diagram cover trend and WIP reasonably well and are underused, but for per status time most teams I've worked with end up exporting via JQL into a spreadsheet or reaching for a marketplace app, because there's no first class report for it. So to your third question, the single biggest thing that would make this easier inside Jira is native per status time reporting, with outliers visible, without having to leave the board.