Cycle time of issue seems incorrect in Control Chart

Sabina Grigorescu

Hi,

 

I was analyzing our Control Chart and saw an issue that has a cycle time of 27 minutes. The issue was initially moved from TO DO to IN PROGRESS on the 19th of May 2022. It was then moved on the 27th of June at 2:04 PM from IN PROGRESS to TO DO. On the same day, the colleague working on it moved it at 2:32 PM from TO DO to IN PROGRESS. And it has stayed IN PROGRESS ever since. So my question is now: why is the cycle time of this issue 27 minutes? Thanks!

Emre Toptancı [OBSS]

Hello @Sabina Grigorescu

Control Chart provides little insight into its inner workings and offers limited flexibility in terms of report parameters. Our team at OBSS built Timepiece - Time in Status for Jira for this exact need. You can even install it as a free trial version to cross-check its results with the Control Chart. The app 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 and on each assignee.

       

The app has Consolidated Columns feature. This feature allows you to combine the duration for multiple statuses into a single column and exclude unwanted ones. It is the most flexible way to get any measurement you might want. Measurements 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 customer (organization) 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.

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.

And the app has a REST API so you can get the reports from Jira UI or via REST.

  

Using Time in Status you can:

• See how much time each issue spent on each status, assignee, user group and also see dates of status transitions.
• Calculate averages and sums of those durations grouped by issue fields you select. (For example, see average InProgress time per project and per issue type.)
• Export your data as XLS, XLSX, or CSV.
• Access data via REST API. (for integrations)
• Visualize data with various chart types.
• See Time in Status reports on Jira Dashboard gadgets

Timepiece - Time in Status for Jira

EmreT