Visualize sprint progress with Tempo Burndown Reports. Track time, forecast accurately, and stay on schedule – all within Jira.
Burnup reports
Burnup reports visualize how much work has been completed over time – while also showing how scope changes affect delivery.
A burnup report shows how much work a team has completed over time – while also showing how scope changes affect delivery. Unlike burndown charts, which focus on remaining work, a burnup visualizes completed work against total scope, making progress easy to read even when requirements shift.
With Tempo Timesheets, burnup reporting goes beyond story points. By grounding progress in logged time, Tempo helps teams, managers, and stakeholders see how real effort translates into delivery across sprints, projects, and long-running initiatives.
What is a burnup report?
A burnup report is a chart that plots two lines over time: Completed work (how much has been finished so far) and total scope (the full amount of work planned, including any changes).
As work gets done, the completed line moves upward. When scope changes – such as new work being added – the total scope line shifts to match. That makes burnup reports useful in environments where scope is expected to evolve.
Jira and agile teams use burnup reports to track delivery progress without masking scope changes, communicate progress to stakeholders, and support forecasting for releases or longer-term initiatives. Burndown charts are more common, but some teams prefer to see how much work they have done rather than how much they have left. Scope creep is easier to spot in a burnup.
The value of burnup reports
Burnup reports offer clarity where traditional reports fall short. They keep teams honest when scope changes. Instead of hiding scope creep, burnups make it visible – so teams can respond early.
Stakeholders can see what has been completed and how scope has evolved. By comparing the pace of completed work to the pace of scope growth, teams can forecast delivery timelines with more confidence. When work is added mid-stream, burnups avoid the confusion that can arise in burndown charts.
Burnup reporting with Tempo Timesheets
Tempo brings a time-based perspective to burnup reporting by combining Jira issue data with worklog data from Tempo Timesheets.
With Tempo, burnup reporting can reflect logged hours instead of estimates alone, progress across multiple teams or projects, and effort invested over time – not just task completion.
Because Tempo captures when and where time is logged, burnup reports can show how completed effort accumulates against planned or total scope, giving a more reliable view of delivery.
What makes Tempo's burnup reporting different
Time-based progress, not just story points
Most burnup reports focus on issues or story points. Tempo adds depth with burnup views based on time logged, so teams can see how effort translates into outcomes.
Flexible scope across Jira
Tempo's reporting and integrations let burnup reports span multiple Jira projects, epics or initiatives, and teams, roles, or accounts. That makes burnup reporting useful for sprints as well as cross-team initiatives and long-running work.
Works inside Jira
Tempo Timesheets is built for the Atlassian ecosystem. Teams log time, manage work, and analyze progress without leaving Jira – reducing friction and improving data quality.
Powerful reporting and visualization
Combine Timesheets with Structure or Custom Charts for Jira to build burnup visualizations that reflect complex scopes, evolving work, and real delivery patterns.
Create burnup reports with Custom Charts
If you want to stay on top of project progress and catch scope creep, a burnup report is the right tool. With Custom Charts for Jira and Confluence, you can build highly customizable burnup reports on a Jira dashboard or Confluence page.
Standard Jira burnup charts
Jira ships with a burnup chart out of the box. It's a project report, not a dashboard gadget – so you can't add it to a Jira dashboard, and you can't customize it.
The standard Jira burnup chart also reports on a single sprint only. You can't view progress on an epic or release, and you can't see more than one sprint at once. That's a problem for enterprises with multiple agile teams that need progress across all their work.
Build flexible burnup reports with Custom Charts
Custom Charts lets you build issue-history reports on Jira dashboards and Confluence pages.
With Custom Charts, you can build burnups of individual or multiple sprints, epics, releases, teams, and projects. That's useful for individual agile teams and Scrum Masters or product owners, as well as program managers who want a bird's-eye view of whether every team is on track.
With a wide range of customization options, you can shape burnups to match the needs of your team and stakeholders.
Add the Custom Charts gadget to a Jira dashboard, or the Custom Charts macro to a Confluence page. To create a burnup or burndown, choose a 2D chart, select "Issue History" from the Chart By dropdown, and "Status" from the Group By dropdown.
Create time-based burnup reports with Timesheets
If you use Timesheets to track time on customer accounts, you can build a burnup that shows the progress of hours worked on an account.
Use the Account Custom Budget Burnup Gadget on your Jira dashboard. You can insert a custom budget (using the Insert goal field) and period. The gadget gives you flexibility in how data is visualized and helps managers and executives monitor account progress, plan resources, and allocate capacity.
Accurate, consistent time tracking is the foundation of a useful Timesheets burnup. Encourage your team to log time regularly so the data stays reliable.
When new work is added, the total scope line adjusts – making scope growth obvious. Managers review progress trends to assess delivery risk and capacity. Stakeholders use the report to understand progress without misreading scope changes.
Best practices for burnup reporting
Log time consistently so burnup data reflects real effort. Review scope changes regularly to understand their impact on delivery. Use burnups alongside burndowns for a balanced view of progress and remaining work.
Filter reports by team or project to see where effort is concentrated. Use historical burnup data to improve future planning and forecasting.
Get more from your agile reporting
Tempo Timesheets turns burnup reports into a reliable source of truth by grounding progress in real work performed. By combining time tracking, flexible reporting, and deep Jira integration, Tempo helps teams move past surface-level metrics and gain confidence in how progress, scope, and effort line up.
Credit reporting giant TransUnion saved $750,000 annually using Timesheets. See how they did it.
Timesheets
Optimize your projects, teams, and resources
The #1 time-tracking app for Jira. Timesheets seamlessly integrates with Jira and your existing workflows to help you track time for accounting, CapEx tracking, client billing, compliance, and more.
Start a Free TrialFrequently Asked Questions
Couldn't find what you need?Go to our documentation
Use a burnup chart when your project scope is likely to change during execution or when you need to communicate progress to stakeholders who need visibility into scope growth.
Burnup charts excel in environments where requirements evolve, new features are added mid-project, or scope creep is a concern. They show both completed work and total scope as separate lines, making scope changes immediately visible. This prevents the misleading picture that can occur with burndown charts, where adding new work can make a team appear to be falling behind even when they're completing tasks on schedule.
Burndown charts work better for fixed-scope sprints where the focus is on completing a predetermined set of work. For long-running initiatives, product development, or projects with external dependencies that might introduce new requirements, burnup charts provide clearer communication and reduce misunderstandings about progress versus scope changes.
Burnup velocity measures how quickly your team completes work over time, helping predict future delivery timelines. Calculate it by measuring the amount of work completed in a given time period – typically a sprint or week.
For story point-based burnup charts, velocity is the number of story points completed per sprint. For time-based burnup reporting in Timesheets, velocity represents the hours of work logged and completed per time period. To establish a reliable velocity baseline, average the completed work across multiple recent periods (typically 3-5 sprints). This smooths out anomalies from holidays, team changes, or unusual circumstances. Once you have average velocity, you can forecast completion by dividing remaining scope by velocity.
For example, if your team completes 80 hours per week and has 240 hours of scope remaining, you can forecast approximately three weeks to completion – assuming scope remains stable.
Yes, burnup charts work well for Kanban teams, though the approach differs slightly from sprint-based agile. In Kanban, burnup charts typically track cumulative flow of completed work items over time rather than against sprint boundaries.
Since Kanban focuses on continuous delivery rather than time-boxed iterations, the burnup chart becomes a tool for visualizing throughput trends and delivery predictability. The total scope line might represent a release target, quarterly goal, or rolling forecast rather than a fixed sprint commitment.
Tempo Timesheets supports Kanban workflows by tracking time logged across continuous work streams, allowing teams to build burnup views based on actual effort invested. This helps Kanban teams demonstrate progress, identify when work-in-progress limits are being respected, and forecast completion dates for larger initiatives even without formal sprint structures. The key is maintaining consistent work item sizing or using time-based metrics rather than story points.
Related articles
Discover the best Jira dashboard examples to track sprint progress, visualize key metrics, and customize reports for a more efficient workflow.
Master Jira reporting basics to track project progress, analyze team performance, and make data-driven decisions with built-in report types.
Learn how to use velocity charts in Jira to track progress, improve sprint planning & make data-driven decisions for better agile project management.
Issue history reporting in Custom Charts for Jira & Confluence lets you make burndown reports for sprints, epics, and releases across multiple teams.
The Jira Sprint Report supports and facilitates the micro-planning that should be happening in your daily stand-ups, enabling you to stay on track.
Jira Version Reports provide excellent visibility of your delivery timeline so that scrum teams can manage risk and identify uncertainty.
With a deep understanding of your team’s activity, you’ll be better equipped to make the decisions that matter.
If you’re a project management professional, avoiding scope creep increases the chance of delivering the project on time and on budget.
