How "Include non-working days in calculations" works

Question

Hi there,

I have configured my non working days as in https://community.atlassian.com/t5/Jira-Software-questions/How-are-quot-non-working-days-quot-in-the-Control-Chart-sourced/qaq-p/1799974.

if I click "Include non working days in calculations" in my control chart, average time for my filter is 4w 18h 20m. If I deselec it, result is 2w 6d 6h

Apparently is working ok, cause numbers are different. This creates me some questions:

- if average time spent in progress in reality has been 4 weeks, shouldnt JIRA show 4 weeks regardess jira is counting weekends or not. My logic says it should be 4 weeks of 5 days or 4 weeks of 7 days, but anyways 4 weeks

-if JIRA is storing time in days every new 24 hours, first option could be 4w of 5 days =20d and second option is 2w of 7 days=14+6d=20d.  Does this means first calculation is removing weekends (where is the time spent on weekends then?), so choice to take for almost all companies? Another clue to support this theory is that second option has 6d in calculation.  so counting saturday. How is it done? Why time spent is higher if I chose "include non working days in calculation"?

-to me, looks like Jira has just built weeks of 5 or 7 days to divide whole amount by them, depending on selecting or unselecting this button, but that's differrent from removing time tasks have spent on weekends

-Can anyone explain the logic behind this button??

Many thanks!

21

Emre Toptancı [OBSS] · Answer

Hello @[deleted],

Control Chart is not very transparent about its inner workings and has very limited flexibility.

If you are OK with using a marketplace app for this purpose, our team at OBSS built Timepiece - Time in Status for Jira app for this exact need and more. 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 and each assignee.

You can calculate averages and sums of those durations grouped by the issue fields you select. For example average resolution time per week, month, issuetype etc.

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.

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.

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 · Answer

Hi @[deleted]

My understanding of this charts calculations is that Jira uses your project settings for working days and site setting for time tracking, working hours, with the defaults as Monday-Friday and 8 am to 5 pm.  And when you include weekends, it includes the other days' hour counts.

So a "week" would be your working day count x work hours in total hours.

Please try this: create a quick filter to narrowly define what is shown on the control chart, and review the results.  Then look at the history of the individual issues shown on the chart to learn their time values.  Finally check your settings for working days and hours can compare the results.

And also...there is a subtlety to how Atlassian computes the average, which they explain as improving the usefulness, accuracy of the value.  You may read about that here: https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-control-chart/

And here: https://support.atlassian.com/jira-software-cloud/docs/methods-of-calculating-rolling-average-on-the-control-chart/

I did this by hand one time to verify some automation rules and it turned out to be working as designed.  If you find otherwise, please post more details for the community to offer ideas.  Thanks!

Kind regards,
Bill