Learn how to set up Jira Software Cloud and integrate it with other products and applications.
Learn how to configure your Jira Software Cloud company-managed projects to suit your agile development processes.
Learn how to create, search, and work with issues in software projects, manage your profile, and more.
Learn how to get started, enable features, and manage and administer team-managed projects.
Plan and view work across multiple teams, projects, and releases with Advanced Roadmaps.
A guide on how to deploy and monitor an application built on AWS using Atlassian and third-party tools.
This page is for team-managed projects
If the lower-left of your project sidebar says you're in a company-managed project, check out these company-managed project articles instead.
Learn more about the difference between company-managed and team-managed projects.
The Burnup report tracks your team's progress as they complete a sprint. It shows the amount of work that has been completed and compares it with the work that was planned. This helps you identify problems such as scope creep or a deviation from the planned project path.
Before you begin
In team-managed projects, the Burnup report can only be used if you have the Sprints feature enabled. Learn more about sprints.
How to read the Burnup report
The vertical axis represents the amount of work, measured either by story points or number of issues. The horizontal axis represents time in days.
Work scope (the red line) shows the work that was planned for the sprint. If this line increases throughout the sprint, this is a sign of scope creep.
Completed work (the green line) shows work that has been moved to Done, and the Done status is in the rightmost column on the board.
Guideline (the grey line) shows an approximation of how your team should be progressing throughout the sprint to finish on time.
The distance between the Work scope and Completed work lines on the chart is the amount of work remaining. When all work for the sprint is complete, the lines will meet.
Things to keep in mind
If the Estimation feature has been enabled, your report will display using your team's story point estimates for each issue.
If Estimation hasn't been enabled, your report will display using the number of issues, which means they will treat each issue as having equal weighting.
The report does not use data from subtasks, even if your project's subtasks have their own estimates. The report will only use data from standard-level issue types like Stories, Bugs, or Tasks.
Was this helpful?