You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.
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.