Seems like something that should be fixed, the data is wrong and now I have to manually calculate since I want business days.  Basically, this report only reports for all days not business days until this bug is fixed.  It would be better than for me to be able to configure the report to display days and not convert to weeks, I don't see a way to do this, is this possible?

This is a basic thing that is needed to make this chart useful and should have been fixed years ago.

I've resorted to always checking "Include non-working days in calculations"

• It's immediately relevant to audience in real calendar concepts
• It avoids the gnarly "pure KPI metric" conversation detangling "weeks" meaning "containers of 7 working days"

I think this is an intentional "feature" to springboard customers to buying community add-ins that do it right.  If one could ever find such a set.

There is no use for the charts if they don't represent relevant info. This is a part of basic stuff for the charts - please fix this.

Adding a +1 to this.  It's been almost 5 years since this reported, any update to share on a fix for this?

Hi there, this issue has been impacting my team since 2019. I figured out by manually calculating cycle time for a few individual issues that the 1w actually equates to seven working days. So a 1w 3d on my control chart actually means 10 working days total. To avoid confusion, I report my cycle time in number of working days. That doesn't resolve the issue, though. 

It's been a year since I've looked at the control chart and I'm disappointed to see this is still an issue. I had to revisit to remind myself of the calculations. What would it take to get this addressed? Cycle time is a key Agile metric!

In the absence of this bug fix is there any help on how to interpret the charts data. Like should Avg time 23 h be treated as 23 hours to close an issue and Median like 1d 2h be treated as 26hs to close an issue? It is confusing how to interpret this data.

I can't understand why Atlassian won't document how to read the chart data but leave it with explanation that is inadequate in their sites.

Seeing that this is 2 years old, and  ranked low (for reasons unknown as this is not a cosmetic bug) i don't see this getting fixed for a long time to come.

Agree with the previous commentators on this. It undermines team's faith in reports. Having an unreliable inaccurate reporting mechanism is even worse than having no reporting at all. It impacts teams' abilities to accurately assess cycle time and to plan work. Please fix!

this one is a real pain and like Igor says above, it really does make teams doubt these reports  

Please fix - especially for those who are using these charts on a quarterly basis for reporting purposes. thank you

Please fix it. It's extremely misleading and makes teams doubt the usefulness of Jira reports at all ;(