Regarding calculation of Control charts.

[balaji]

Hi Team,

When creating reports with Jira (control diagram) and checking for cycle times, I sometimes get results like 7w 5d 5h when I explicitly exclude workfree days (corresponding checkbox not checked). How is this possible? In the example it should read 8w 0d 5h since 1w = 5d = 24h.

Please refer the below attached screenshot:-

Highlighted time should show 2w 1d 22h.

Thanks

[Mehmet A _Bloompeak_]

Hi @balaji 

As an alternative, you can try Status Time Reports app developed by our team. It provides various cycle time reports and you can define your own working calendar. For further details, you can have a look at our article below. Hope it helps.

Cycle Time and Lead Time in Jira: Productivity Measurement with Two Critical Parameters  

[Emre Toptancı _OBSS_]

Hello @balaji ,

Jira's Control Chart works like a black-box and has very limited flexibility. If you are interested in a much more capable and flexible solution, let me recommend our app Time in Status. It is available for Jira Server, Cloud, and Data Center. 

Time in Status basically 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 week, month, issuetype, request type, etc. The ability to group by parts of dates (year, month, week, day, hour) 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

[Bill Sheboy]

Hi @balaji 

Some things of note when using Atlassian's interpretation of a control chart:

• Their "cycle time" measurement uses date/time events and the Jira settings for working days and hours.  So there could be more/less days than you expect if the events occurred outside of the normal working hour boundaries that Jira uses, 9 AM - 5 PM with 5 days per week: Monday - Friday.  It does not use 24h days.
• In your example about working and non-working days, do you mean weekends only or also the non-working day settings for the project?
• You have highlighted the median value, which would be the middle value for all issues noted (for the data range and filter), yet that does not match the differences you noted.  Did you highlight something else?

Kind regards,
Bill