Why can't I see the first sprints info in the burndown chart?

[Oscar Caballero]

I'm looking for historical data from the project and the burndown chart only shows information from the Sprint 3 to the last one but Sprints 1 & 2 are not appearing to be selected.

Note: Sprint 1 & 2 were initiated less that a year ago.

[Trudy Claspill]

Hello @Oscar Caballero 

Welcome to the Atlassian community!

Using Advanced Issue Search can you confirm that there are issues from that project that are still listed as assigned to Sprint 1 and Sprint 2?

[Oscar Caballero]

Hi Trudy.

Yep... I used the filter and confirmed also in the issue's detail section; I even counted them one by one.

look:

[Christopher Maxwell]

Hi Oscar,

Are you referring to the epic burndown chart?

What are the dates of Sprints 1, 2, 3, and 4?

[Oscar Caballero]

Hi Chris.

I'm referring to the "standard" burndown chart, the one that considers all issues planned during the Sprint and tells you the work done.

Dates:

Sprint 1 - Feb 8th

Sprint 2 - Feb 22nd

Sprint 3 - Mar 9th

Sprint 4 - Mar 23rd

[Christopher Maxwell]

Hi Oscar,

I've done some testing and haven't been able to figure this out yet.

I did, however, come across something for Data Center where a release is created and then the first issue created in the first sprint associated with the version establishes a baseline for the initial sprint (https://confluence.atlassian.com/jirakb/some-completed-sprints-are-not-visible-in-the-release-burndown-report-859470935.html    "Cause" section).

I know you are on Cloud, but is it possible that releases started to be used with Sprint 3?

[Oscar Caballero]

Yes, I know it's kind of weird...

Reading about the versions in the link you shared maybe it's possible that some done tasks were added to the version after the sprint ended. I'll check that out.

What puzzles me the most is that at the beginning of the project, in the first sprints, those reports were just fine, the info was displaying good for the burndown and the burnup charts but now they don't.

Thanks Chris!