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

Jira Release Burndown chart issues when working in parallel sprints

Ashish Sharma
Contributor
November 27, 2018

We have parallel sprints option enabled in Jira, as multiple scrum teams work in their own respective sprints. Only one team's issues are linked to a specific version. 

However when i am seeing release burndown chart plotted against any fixVersion, it is super confusing. It is including sprints in charts where there are no issues linked with that specific fixVersion, also if I scroll down it lists issues in sprint bucket which is not correct as against few of the sprints - issues are mentioned which are not in that sprint.

This is super confusing, and as scrum master I am unable to explain this to any of the stakeholders? Why is release burndown including sprints which don't have anything tagged to respective versions, and why are the issues wrongly placed in sprint's bucket. How can we make of use in parallel sprints mode?

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
atlassian, team '25, conference, certifications, bootcamps, training experience, anaheim ca,

Want to make the most of Team ‘25?

Spend the day sharpening your skills in Atlassian Cloud Organization Admin or Jira Administration, then take the exam onsite. Already ready? Take one - or more - of 12 different certification exams while you’re in Anaheim at Team' 25.

Learn more
AUG Leaders

Upcoming Jira Events