Control Chart not counting an issue for August that began Dev in August

[Grace Hamer]

Hi Atlassian Community,

Can someone please explain why this issue was not included in the August Control Chart since it began development in August? It's instead being included in the September chart, therefore, throwing our cycle time off

Moved from Backlog -> Development 26/08/2025

Development -> Done 01/09/2025

The ticket did not move back to Development during the life cycle. The last update that was made to it, after Done was to change its Work Subcategory

Thanks

[Gor Greyan · Accepted solution]

Hi @Grace Hamer

The Control Chart groups issues by their completion date, not when development started. Since this issue was moved to Done on 01/09/2025, it’s included in the September chart, even though work began in August.

https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-control-chart/

[Birkan Yildiz _OBSS_]

Hi @Grace Hamer ,

This is a very common point of confusion. Here is the direct answer:

The Jira Control Chart groups issues by their completion date, not their start date. Since your issue was completed (moved to "Done") on September 1st, the chart is working as designed by placing it in the September data bucket.

This bucketing is the first reason your cycle time feels "off." The second, more critical reason is that Jira's built-in reports calculate cycle time 24/7, including nights, weekends, and holidays. This can significantly increase your metrics and hide where the real bottlenecks are.

If you need accurate Cycle Time and Lead Time reports, a dedicated marketplace app is the best solution.

Timepiece - Time in Status for Jira is built for this. Its biggest advantage is that it allows you to create custom work calendars (e.g., Monday-Friday, 9:00 AM - 5:00 PM).

When you run a Cycle Time report in Timepiece, it calculates based on your actual working hours, giving you a true, accurate measure of your team's performance, not an inflated number.

It also works on all your existing historical data, so you can install it and get accurate reports for your August 2025 issues today. 
Hope this helps. Please let me know if you have any further question, and visit Timepiece’s marketplace page.

[Rahul_RVS]

Hi @Grace Hamer 

Welcome to the community !!

To calculate cycle times, if you would be interested in a mktplace app, I can suggest the one we have developed :

Time in Status Reports 

The Time between statuses report or the status grouping feature are 2 ways in which the app helps to calculate the cycle time of your issues. Do give it a try !!

More details here.

Disclaimer : I am part of the app team for this add-on

[Grace Hamer]

thank you - is there anyway to change this as cycle time should be counted from when an issue is moved to development?

[Iryna Komarnitska_SaaSJet_]

Hi @Grace Hamer ,

Jira’s Control Chart includes issues based on the date they were completed, not when work began. Since your issue moved to Done on 01/09/2025, it appears in the September chart. The chart still measures cycle time from the first “in progress” status (e.g., Development) to Done, but it’s only plotted in the month it was completed. There’s no built-in way to backdate that; the workaround is to widen the date range (to include Sept 1) or use a different report.

If you don't mind using third-party apps, you can try the Time in Status app developed by my team at SaaSJet.

It allows you to create custom group statuses and accurately calculate Cycle Time according to your needs.