How Jira deals with days in Control Chart

[Alexandre]

My control chart is showing an average cycle time of 2w 6d 5h (non working days unticked) but the working days are configured as monday - friday (5d). Shouldn't this show 3w 1d 5h?

[Zoryana Bohutska _SaaSJet_]

Hi @Alexandre 

Also, you can consider other tools from the marketplace to generate reports of Cycle and Lead Time. For example Time in Status for Jira Cloud and Time Between Statuses add-ons. You can read more information about them and the Control Chart at this article 3 tools to analyze Cycle and Lead Time in the Jira

Hope it will help you

Regards

[Emre Toptancı [OBSS]]

Hello Alexandre,

There is a known bug about Control Chart for what you mentioned. The Atlassian issue below is for Jira Server but Jira Cloud probably has the same problem.

https://jira.atlassian.com/browse/JSWSERVER-16449

If you are interested in a ready built alternative solution, our team at OBSS built Timepiece - Time in Status for Jira app for this exact need. It is available for Jira Server, Cloud and Data Center.

Time in Status allows you to see how much time each issue spent on each status or assigned to each assignee or group. You can combine statuses into consolidated columns to see metrics like Age, Resolution Time, Cycle Time or Lead Time. For these metrics, you can individually select which statuses to include or exclude. All durations can be display in various formats including days, hours, minutes even seconds.

It can calculate averages and sums of those durations grouped by issue fields you select. (For example see the average Cycle Time per project and per issuetype or see the sum of InProgress time per component). 

Time in Status uses Jira issue histories to calculate its reports so you can use the app to get reports on your past issues as well.

The app has custom calendar support so you can get your reports based on a 24/7 calendar or your custom business calendar. (This one is important because a 24/7 calendar in most cases shows misleading data. For example an issue created at 16:00 on Friday and was resolved at 09:00 on next Monday seems to stay open for 2,5 days but in terms of business hours, it is only a few hours. You can see this using Time in Status by OBSS.)

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. Get metrics like Lead Time or Cycle Time.
• Calculate averages and sums of those durations grouped by issue fields you select. (For example see average InProgress time per project and per issuetype.)
• Export your data as XLS, XLSX or CSV.
• Access data via REST API.
• Use one of various charts type for your reports.

Timepiece - Time in Status for Jira

EmreT