Although I understand the defination which says:
But if you see the graph, more or less they represent the same.
The burndown chart has more of a focus on day-to-day activities. Below the chart, you will see a an overview of updates on issues. When an issue is added to a sprint, a status change occurs or work has been logged. All these events are entries that are logged and displayed below the chart when they occur.
The sprint report shows you a list of issues and groups them into completed / not completed / removed from sprint (and shows an asterisk to mark issues added after the sprint start.
In short, the burndown chart and the change history that comes with it aims to give you detailed and almost real time insights into how your sprint is progressing. The sprint report is better suited for snapshot like intermediate checks (it has less information, but is easier to read) and retrospectives. Which is why the sprint report can also be linked to a retrospective page in Confluence.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Atlas Camp is our developer event which will take place in Barcelona, Spain from the 6th -7th of September . This is a great opportunity to meet other developers and get n...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs