Cycle time report no data is found

[Qais Alkhatib]

Hello folks,

our project has many sprints were released previously, but in cycle time report shows no data. how i diagnose the issue and make it work? your help would be highly appreciated. thank you

[Valeriia_Havrylenko_SaaSJet]

Hello @Qais Alkhatib  👋

If you're looking for add-on, you can try Time in Status for Jira Cloud (developed by my SaaSJet team). Create the Cycle or Lead time report easily and display it on your board and export it to CSV or XLSX files for further analysis.

All you need is to:

• create a status group;
• choose statuses;
• click the "Save" button.
  
  
  
  

As an alternative, you can try a solution described in this short use case on how to get Cycle and Lead time for Jira issues. 

Also, you can read the article which describes some ways to get the Cycle time report for your issues.

Add-on has a 30-day free trial version and free up to 10 users. 
Please, let me know if you have any questions

Hope it helps 😌
Valeriia 

[Walter Buggenhout]

Hi @Qais Alkhatib,

The report is based on an integration with your CI/CD tools and there's a couple of things involved before you would see the data you're looking for:

• a working connection to your CI/CD tools must be set up
• you need to have enough production data in place and they need to meet certain criteria (deployment events from CI/CD tools, commit events from your source code management tool, issue keys referenced in branch names, commit messages, pull requests)
• project permissions must be set correctly (view development tools)

Check out this support article for more details on everything you need to make this work.

Hope this helps! 

[Bill Sheboy]

Hi @Qais Alkhatib 

Adding to Walter's answer...

If you want to measure the issue cycle times (e.g., time from/to specific status values) you can use the built-in Control Chart instead.  That chart does have some limitations, so please review this documentation/suggestions to learn how it can help:

https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-control-chart/

Kind regards,
Bill

[Charlene B]

@Walter Buggenhout  
"you need to have enough production data in place and they need to meet certain criteria"
How much is enough?
On the support page it say "You cannot see the review time until sufficient historical data is available for your PRs."  but does not define what "sufficient" is.

The control chart is no longer there and that was MUCH more flexible!

[Mehmet A _Bloompeak_]

Hi @Qais Alkhatib

For cycle time, you can try Status Time Reports app developed by our team. It mainly provides reports and gadgets based on how much time passed in each status

Here is the online demo link, you can see it in action and try without installing the app. For your case, you can have a look at Cycle Time by Assignee report, Cycle Time by Components report, Cycle Time by Project report, Cycle Time for Each Issue report, Cycle Time by Issue Creation Month report as examples.

For more detail, you can have a look at Cycle Time and Lead Time in Jira: Productivity Measurement with Two Critical Parameters article and Status Time Reports How to Videos.

If you are looking for a completely free solution, you can try the limited version Status Time Free.

Hope it helps.

[Emre Toptancı _OBSS_]

Hello @Qais Alkhatib

I can offer a solution that provides metrics like Cycle Time, Lead Time, etc which works only based on your issue workflows and does not require a CI/CD system integration.

Our team at OBSS built Time in Status for this exact need. It is available for Jira Server, Cloud, and Data Center.  

Time in Status mainly allows you to see how much time each issue spent on each status or each assignee. 

   

You can combine the time for multiple statuses to get metrics like Issue Age, Cycle Time, Lead Time, Resolution Time etc. 

For all numeric report types, you can calculate averages and sums of those durations grouped by the issue fields you select. For example total in-progress time per Vertical or average resolution time per sprint, week, month, issuetype, request type, etc. The ability to group by parts of dates (year, month, week, day, hour) or sprints is particularly useful here since it allows you to compare different time periods or see the trend. 

The app calculates its reports using already existing Jira issue histories so when you install the app, you don't need to add anything to your issue workflows and you can get reports on your past issues as well. It supports both Company Managed and Team Managed projects for Jira Cloud.

Time in Status reports can be accessed through its own reporting page, dashboard gadgets, and issue view screen tabs. All these options can provide both calculated data tables and charts.

  

https://marketplace.atlassian.com/apps/1211756/

EmreT