Get Cycle Time for Specific Time as a Number

[Kim_Vencill]

There is interest in seeing cycle time for all work items for specified period of time as a average number.  See below example from ADO. 

In Jira I can get the average cycle time line graph in Jira reports, but I'm trying to find a way to get the average days like ADO. 

Control chart provides some of glimpse but isn't configurable to specific issue types.

Anyone have any advice if this is possible? 

Anyone 

[Birkan Yildiz _OBSS_]

Hey @Kim_Vencill

If you are open to using a Marketplace app, you can easily get this exact average number using Timepiece - Time in Status for Jira.
Here is how you can set it up to get your average cycle time number:

Filter your Scope: Use the app's JQL filter option to select your specific issue types and the exact time period you want to analyze.
Define Cycle Time: Select the Status Duration report and use the Consolidated Columns feature to group all of your active work statuses (like 'In Progress' and 'In Review') into a single "Cycle Time" column.

Get the Average: Change the report option in the top menu from a standard list to an Average report. This will instantly aggregate the data and provide the exact average cycle time number for your selected issues. You have many options for grouping when getting the Average Time. We used Created Month and Created Year in this example, but you can choose any Jira Field or Custom Field, such as Issue Type or Priority, for your grouping.

Add to Dashboard: Timepiece includes a highly customizable Dashboard Gadget. You can place this exact average report directly on your Jira dashboard to see the number at a glance.

Pro tip: You can also configure the report to use Custom Calendars. This ensures your cycle time calculation automatically excludes weekends, nights, and public holidays, giving you an accurate number based on actual business days rather than a 24/7 clock.

You can find Timepiece - Time in Status for Jira on the Atlassian Marketplace.

Full disclosure, I'm on the team that makes Timepiece. Hope this helps you get the exact metric you need!

[Rahul_RVS]

Hi @Kim_Vencill 

As James suggested, a mktplace app can help here. For detailed reporting for cycle times / time in status for your issues, if you would like to try out one, pls explore

Time in Status Reports 

With this app you generate time in each workflow status for multiple issues with multiple filter and grouping options. It works for current issues and closed ones as well.

The report below shows the cycle time of the issues.

The app can be easily added as a dashboard gadget and can be shared with colleagues.

More details here.

Disclaimer : I am part of the app team for this add-on 

[Alexey Pavlenko _App Developer_]

Hi  @Kim_Vencill ,

Yes, the Control Chart is not configurable, unfortunately.

With my app AI Code Pulse: Total Cost and Efficiency of AI-coding you can track PR Cycle Time for any period and get average, plus:

• Rework rate - code waste and survivability, missing implementation parts - this is one of the few crucial signals for measuring your AI coding efficiency.  
• AI model cost, input/output token and cache usage - measure how efficiently you craft prompts and use cache in correlation with feature or engineer seniority. These metrics can also be useful for Token Maxxing advocates. 

 

Best regards,
Alexey

[Danut M _StonikByte_]

Hi @Kim_Vencill,

You can try the Control Chart report of Jira, but it is not customizable. 

Otherwise, if you are open to using a plugin from Atlassian Marketplace, your best choice will be the Control Chart gadget offered by our Great Gadgets app.

It is higly configurable, allows JQL as data source so you can include the issues you want.

If you have any questions, feel free to contact us at support@stonikbyte.com. 

Danut.  

[Khrystyna_Dzhus_SaaSJet_]

Hi @Kim_Vencill ,

If you're open to a Marketplace app, this is exactly what Time in Status can do — and it can give you the single average number, not just a chart.

For the ADO-style KPI:

1. In Columns → Status Groups, create a group called "Cycle Time" and add the statuses that represent your delivery phase (e.g. In Progress → Ready for Release). This collapses cycle time into one column.

2. Run the Time in Status report, scope it to a period (Filter / Trim period range) and filter to a specific work item type via JQL (e.g. issuetype = Story).

3. Open Report Summary — it shows items count, total, and the average for your Cycle Time group across all matching issues. That average is your single number, like ADO.

If you also want to watch how that number moves over time, run the Average Time report with the same Cycle Time group and pick an interval (Daily / Weekly / Monthly / Quarterly) — you'll get the average cycle time per period.

You can change the time format (e.g. decimal days) and export to XLSX/CSV if needed.

Disclaimer: I'm part of the Time in Status team at SaaSJet.

If you have any questions, I would be glad to answer.

[Alina Chyzh_Grandia Solutions]

Unfortunately, Jira's native Control Chart doesn't allow filtering by specific issue types, and the built-in Cycle Time report only provides the line graph view you mentioned, not a single average number like Azure DevOps shows. You could manually export the data and calculate it in a spreadsheet, but there's no out-of-the-box way to display that average directly in Jira's interface.

If you're looking for a more flexible approach, our Marketplace app Report Hub might help. It includes an Average Time to Resolution report that can be filtered by issue type and calculates the average cycle time across any specified period, showing it as a clear numerical value. You can configure it to show cycle time per status, per user, or across your entire workflow depending on what you need to track. You can check it out here: https://bit.ly/4cbZyIZ

[Anastasiia Maliei SaaSJet]

Hi @Kim_Vencill,

If you’re open to using a Marketplace app, this use case can be covered with Time Metrics Tracker.

In the app, you can create a custom Cycle Time metric by selecting the start and end statuses of your workflow. Then you can run the report for a specific date range — for example, using the resolved date if you want to analyze work items completed during a selected period.

You can also narrow the result by project, board, work item type, status, assignee, sprint, or label. So if you need the average Cycle Time only for Stories, Bugs, or another specific work type, you can filter the report accordingly.

The app calculates the average value for the selected time metric, so you can review Cycle Time as a number, not only as a chart. If needed, you can also change the time format, for example to decimal days, and export the data for further analysis.

For ongoing monitoring, the Trend Gadget can help you analyze the same Cycle Time metric directly on a Jira Dashboard. It shows how the metric changes over time and includes additional indicators such as median, 85th percentile, and 95th percentile. You can also drill down into specific work items behind the trend to understand which issues are affecting the metric.

So, if the goal is to get Cycle Time for a selected period and work item type as a number, and then monitor or investigate the trend behind it, Time Metrics Tracker should be a good fit.

If you have any questions, I’ll be happy to help.

[James Gamble]

Hola Kim,

Jira can get you part of the way there natively, but I don’t think the built-in reports give you the exact ADO-style KPI number you’re showing without some workaround.

The closest native report is the Control Chart. It can show cycle time for a selected period, including the average, rolling average, and standard deviation. The catch is that it’s still a report/chart view, not really a dashboard tile that simply says “11 days on average.”

For filtering to a specific issue type, I’d try adding a board quick filter such as:

issuetype = Story

Then open the Control Chart and apply that quick filter. You can also add more conditions to exclude work items that would skew the result, such as canceled, duplicate, or non-delivery items, depending on how your workflow is set up.

If you have Atlassian Analytics available with your Enterprise plan, that may be the better native option. The Flow Metrics dashboard is closer to what you’re describing because it supports cycle time and can be filtered by project, date range, Jira work type, and labels.

If you need this as a reusable Jira dashboard gadget with a single average-days number, you’ll probably need Atlassian Analytics, a Marketplace app for cycle time or time-in-status reporting, or an export/API calculation. JQL by itself won’t calculate average cycle time, because it can find issues, but doesn’t calculate elapsed time between workflow statuses and average the result.

So my short answer would be: it’s possible natively as a chart through the Control Chart, possibly better through Atlassian Analytics, but probably not as the exact ADO-style single-number tile using Jira’s standard dashboard gadgets alone.

Thanks,

James

[Kim_Vencill]

Thanks for responding. The multiple boards solution did occur to me. I was hoping to avoid that.