Release Burndown no longer showing Sprint data after a workflow change

[astravalters]

We implemented a workflow change (changing which statuses a story moves through, and adding different subtask types). Thereafter we noticed that the Release Burndown no longer shows 7+ sprints worth of data. 

Investigation led us to https://confluence.atlassian.com/jirakb/sprint-report-inaccuracies-after-workflow-change-969514644.html and to https://confluence.atlassian.com/jirakb/some-completed-sprints-are-not-visible-in-the-release-burndown-report-859470935.html.  Neither has resolved nor explained what we are seeing.  A major difference from the KB article is that for us, it is all the sprints previous to the current one. 

The fixversion hasn't changed (start date was and continues to be Dec 1 2019)

- Sprints still exist

- JIRA project not changed

- Sprints were shown in the Release Burndown prior to the workflow change

We really need this reporting data. My only recourse right now is to recreate it outside of JIRA, unless anyone has suggestions. 

[astravalters]

It actually sounds like it might be this open defect  https://jira.atlassian.com/browse/JSWSERVER-16105 

[Mikael Sandberg]

Did you add the new statuses to your board columns? On the board select more > Board settings and click the Columns tab. Make sure that your new statuses are not listed under the Unmapped columns, and if they do, drag and drop them into the right column.

[astravalters]

Thanks for that suggestion. Yeah, it's not that.  Those are all mapped correctly. It's about the Release Burndown, not about the board.