You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Right now Control Chart is only showing an option to include/ exclude the non-working days.
Can you please help me understand where this non-working days are controlled?
Hello @Deepika Dandala
Jira Control Chart offers limited details and flexibility in terms of report parameters. For maximum details and flexibility, I suggest you use a marketplace app.
Our team at OBSS built Time in Status exactly for this. 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.
The app also has custom calendar support. You define multiple calendars, each with its own working days, working hours, and holidays. Then you can get Time in Status reports based on one of those calendars.
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 customer 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.
Here is the marketplace page for Time in Status by OBSS:
Hi @Deepika Dandala -- Welcome to the Atlassian Community!
I respectfully suggest you experiment to learn how the Atlassian interpretation of a control chart works when you make adjustments to the non-working days, particularly anything more complex than what a "weekend" is for the team.
My reasons include this report calculates in 24h days (and fractions of them) for measures, but uses the change history date/time values for issues. The behavior is not defined in the documentation for how de-selecting "Include non-working days in calculations" exactly impacts the results. It certainly does not appear to respect the global, working hours setting for a site, as that applies to estimation, time-tracking features.
And so if you are trying to measure at a finer granularity than whole days, you may want to dig deeper into any results shown before relying upon them for team decision-making. Perhaps even hand-calculate some of the measures from the change history to compare to what this chart shows.