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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi all,
I'm new to Jira, but hopefully this is an easy solution. I have not found this question elsewhere, but if it is somewhere please provide a link.
I've got 1 project, and there are 3 teams working in it. Each team has their own board and backlog. One team works on back-office logic, one team works on the UI, one team works on data stuff.
What I want is 1 burndown chart that shows cumulative progress for the thee teams for each _sprint_. Based the attached image, I want a burndown chart that starts at 300 points (the sum of points for the three teams) and works toward 0 for the 3 week span of the sprint.
What I have is 3 burndown charts (one per team). See attached image. There is a dropdown, and I have to pick which team I want to see the sprint burndown for.
I've created a board that shows all the issues allocated to Iteration 9, but I can't figure out how to tell the Burndown Chart to use that board (or the JQL used to populate that board).
HI @Dennis Reda ,
What it looks like in the screen shot is that you are running 3 parallel sprints. If you want it to all show as one aggregated total...then all the teams must work off the same sprint.
Basically, on your board you should create iteration 9. Then on the other 3 boards, each of them should only show tickets pertaining to their team. Each of the boards will add to the same iteration 9. However, what is configured at the moment is not 1 sprint called iteration 9 but 3 sprints with the names: iterations 9 - team 1, iterations 9 - team 2, iterations 9 - team 3. That's why it broken up down to 3 teams.
Hope this helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Having 3 teams work in the same sprint can get very messy though.
Is there a way to report cumulative sprint burndown for more than one sprint?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.