Quarter Progress Burndown Drilldown charts bug?

[David White]

Today is August 20. This is a burndown graph from this quarter, for a team. They are on track, but looking at the first graph, you'd be asking questions about what is happening that the team seems to be making no progress...



But that would be a very incorrect impression. And the impacts of this bug are the conversations that should not need to happen to reassure managers that the project is still on track. 

The second graph is the true picture, based on the best data that Jira Align has at the time. 
To prove it, the third graph highlights the penultimate data point on the graph (Aug 18), and the final graph is the next data point (Aug 25). 

August 25 is 5 days in the future! There is no valid data for that date yet. The graph should stop at the most recent real data point.

This phenomenon is true for all our teams, in all our TofTs.  

(I have looked at information about sprint burndown charts and things that could cause a similar behaviour. None of those causes apply here for quarterly burndown charts.) 

[Kirill Duplyakin]

The intervals for this particular set of Burndowns depend on the Quarterly Increment date range, and are described in this doc: Program increment progress drill down

Hovering your cursor over the any chart ** line will display detailed data in the following intervals, depending on the range of dates displayed in the chart. These intervals are enforced to ensure good chart performance: 

1. Date range <= 60 days: Intervals provided daily.
2. Date range <= 12 months: Intervals provided weekly.
3. Date range <= 60 months: Intervals provided monthly.
4. Date range <= 120 months: Intervals provided quarterly.
5. Date range > 120 months: Intervals provided yearly. 

I agree it's confusing, especially since the parent level the Burndown charts use daily data. But it is by design currently.

We'll have to open up a feature request on your behalf to change it (please continue working with us in the Support ticket).

[David White]

I'm new to this product, Allan. I (mistakenly) thought this was the right channel. Thanks for the pointer. I'll try Atlassian Support. 

[Allan Maxwell]

Yeah, that's a bad one.

Have you reported this bug to Atlassian Support?  Although they do read these community post (and often respond) I don't think they will create a support issue on your behalf.