We are reinventing the Sprint burndown for next-gen projects!

  • Do you have a hard time meeting sprint commitments? Screen Shot 2019-10-02 at 11.08.40 AM.png

  • Do you want to know the accuracy of your sprint’s estimations? Screen Shot 2019-10-02 at 11.08.01 AM.png

  • Do you want to have an easy way to report your team’s performance to management? Screen Shot 2019-10-02 at 11.08.33 AM.png

If the answer to any of these questions is yes, then you’ll benefit from applying the reimagined Sprint burndown chart for next-gen projects to your sprint.


We reinvented the Sprint Burndown. Screen Shot 2019-10-02 at 11.09.42 AM.png

We heard that you loved using the chart in the Burndown chart in classic projects to see whether there are any scope changes that impacted the sprint.

We also heard that you loved using the sprint summary (called the Status Report) table in the Sprint report in classic projects for team retrospectives and stakeholder reporting.

  • What is important to you is anything that might impact sprint commitments, how you’re tracking towards sprint goals and how you can improve your team in future.

  • Majority of you use both reports, and you loved that they were either helping you to remove blockers during your daily stand-ups or when you were reviewing how your sprints went.

  • There was duplication in functionality and an increased cost for new users in learning how to use and for us in maintaining these 2 reports.

Taking the best elements from the Sprint report and the Burndown chart in classic projects, we are releasing the Sprint burndown chart for next-gen projects, while introducing new functionality that helps you visualise your team's performance better.


What is this report? Screen Shot 2019-10-02 at 11.10.22 AM.png

The Sprint burndown chart shows the total work remaining for the current sprint, and the likelihood of your team completing the sprint on time. It also shows a summary of scope changes and work done throughout the sprint, enabling it to be used in sprint retrospectives.

This report will help you:

  • Track the total work remaining and determine the likelihood of achieving the sprint goal. This helps your team manage its progress and respond accordingly.

  • Understand the work completed or pushed back to the backlog in each sprint. This helps you determine if your team is overcommitting or if there is excessive scope creep.



How do I read it?

  • Estimation statistic: The vertical axis represents the estimation statistic that was selected. Currently, only story points exist for the estimation of each issue. Issue count can also be used.

  • Remaining work: The red line represents the total amount of work left in the sprint, according to the team's estimates. This is reflected through the estimation values linked to the issues.

At the start point, the actual work remaining is the same as the ideal work remaining. As time progresses, the actual work line fluctuates above and below the ideal line depending on this disparity between estimates and how effective the team is.

  • In general, a new point is added to this line each day of the project. Each day, the sum of the time or story point estimates for work that was recently completed is subtracted from the last point in the line to determine the next point.

Guideline: The grey line is approximation of where the team should be, assuming linear progress.


  • If the red line is below the guideline, the team's on track to completing all their work by the end of the sprint, as there is less work left than originally predicted and the project is ahead of schedule.

  • If the red line is above the guideline, it means that there is more work left than originally predicted and the project may be behind schedule.

  • The guideline is a straight line that connects the start point to the end point.

    • At the start point, the guideline shows the sum of the estimates for all the remaining work.

    • At the end point, it intercepts the x-axis showing that there is no work left to be completed.

    • This line is a mathematical calculation based on estimates before the sprint started, and the estimates are more likely to be in error than the actual remaining work.


What did we reimagine for the Sprint burndown chart?

Discover what impacted your ability to deliver your sprint goals. Screen Shot 2019-10-02 at 11.11.11 AM.png

  • A new section after the sprint begins to log scope changes such as:

    • Issues removed from and added to sprint.

    • Estimation changes for issues in sprint.

Screen Shot 2019-09-27 at 8.50.57 AM.png

Visualise the data in the way you deem best, drilling down by sorting. Screen Shot 2019-10-02 at 11.08.33 AM.png

  • New columns for epics and assignees, with the new ability to sort by columns to visualise the progress for each epic and assignee, so that you can unblock developers for high priority epics.


Refresh your eyes with modern design patterns. Screen Shot 2019-10-02 at 11.12.44 AM.png


How do I get this for my next-gen project?

If your project has Reports enabled, you’ll be able to start using it right now.


If not, navigate to Project settings > Features and toggle the Reports feature.

Screen Shot 2019-08-13 at 3.03.30 pm.png

What’s next?

We’ll be monitoring usage and feedback to help us understand the value you’re getting from this report, as this will help us prioritize improvements.


annie October 31, 2019

Very cool, checked this out and this is more helpful than the regular burndown!

Like Ivan Teong likes this
Alp Erguney October 31, 2019

Needs control chart too.

Like # people like this
Adrian Lauber November 1, 2019

Burn Down per Developer, PLEAAAASE!!! :raised_hands: (for not "new-gen" Jira)

Like # people like this
Eudora Linde November 5, 2019

Is there a timeline on creating this for the classic Jira folks as well?

Like # people like this
Ivan Teong
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 14, 2019

@Eudora_Linde we won't be delivering this report for Classic, it is exclusive to next-gen.

James Travers December 2, 2019

Shame it covers non-working days so the lines are not as linear or aligned as in reality...

Like # people like this
olibates December 9, 2019
Keita Nagafuchi December 16, 2019

How can I configure non-working days in this burndown chart?

Gary Chamberlain January 7, 2020

@Ivan Teong are you able to provide any insight on when other reports are coming to next-gen projects? Specifically the release burndown is one i use frequently.

Like vitalii_misko likes this
Adrian Lauber April 14, 2020

"Adrian_Lauber Nov 01, 2019 • edited

Burn Down per Developer, PLEAAAASE!!! :raised_hands: (for not "new-gen" Jira)"

This comment already received 4 Likes, Attlasian how could you ignore it ;)

jpbruno June 4, 2020

What about the sprint burndown chart for those that help to see how do we burn hours (because we decompose user stories in small working chunks. This was in the regular software project type.

Like # people like this
jpbruno July 7, 2020

Hi @Ivan Teong please check my comment on 6/4... Is this somehow in the roadmap?

Like james.love likes this
Ivan Teong
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 7, 2020

@jpbruno I assume you're talking about the time tracking filter in the sprint burndown. We won't be delivering that anytime soon - my suggestion is for you to get a gadget to do that.

Chris Sumedca July 24, 2020

Is the control chart in the Roadmap?

Youssef Halwani August 13, 2020

@Ivan Teong Sorry why is the time tracking filter in the sprint burndown not going to be delivered "anytime soon"? From what I've seen its a feature that has been requested many many times and if gadgets exist doesn't that indicate that there is a strong market demand for it?

Like # people like this
Santosh Banerjee November 26, 2021

How to add 'Priority' to the list of columns?


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events