Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,457,706
Community Members
 
Community Events
176
Community Groups

Release Burndown no longer showing Sprint data after a workflow change

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. 

ReleaseFixVersion.PNGReleaseBurndown_missing_data.PNG

 

2 answers

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

0 votes
Mikael Sandberg Community Leader Feb 13, 2020

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.

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

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events