Sprint Report vs Burnup Chart: Points not completed

[Bud Herz]

Background:
I am comparing the Sprint Report to the Burnup Chart. While the naming convention differs, any points not completed in a Sprint should be the same in both views, correct?

Challenge:
In the Sprint Report for a past Sprint we see 35 points not completed.
In the Burnup Chart for the same Sprint it shows 46 points remained when the Sprint was ended.


What is the discrepancy here?

[Maksym Babenko_TypeSwitch_]

Hello Bud, this discrepancy between Sprint Report and Burnup Chart is a classic Jira quirk. Usually it happens because:

• The Sprint Report only includes issues assigned to the sprint at closure

• The Burnup Chart shows total scope over time, including issues added mid-sprint or removed later

That’s why you’re seeing 35 vs 46 points — it’s likely caused by mid-sprint scope changes or timing of resolution.

How Sprint Health Analyzer helps

Sprint Health Analyzer catch these gaps early and give teams a clearer view of what actually happened.

It gives you:

• Independent Burndown, Burnup and Velocity charts based on actual issue history not just the sprint metadata. 

• Visibility into blockers, cycle time, and status churn that might’ve slowed things down

• A full breakdown of done, incomplete, and churned issues even if they were added or removed mid-sprint

That way, when Jira's native charts leave you guessing, this app shows what really went on in the sprint.

No complicated setup, no time wasted reading docs just the insights you need, right out of the box, right after install.

[Vasyl Krokha _Broken Build_]

Hello, Bud.

In Jira's native Burnup Chart, the remaining work is not explicitly shown on the chart.

I've checked the Sprint Report and Burnup Chart for different sprints on my production environment - here are a few hints that may help you:

1. Burnup Chart - on this chart, the remaining work is the gap as shown below:

2. Sprint Report - the chart itself doesn't provide figures, but they can be found in the Status Report below the chart:

So, in the Status Report, "Completed work" and "Remaining work" match all figures derived from the Burnup Chart.

Let me know if this helps.

P.S. In the context of your request, our Burnup Burndown Chart app may be helpful. It includes:

• Burnup/burndown charts with misc forecasting scenarios for all scopes: epics, initiatives, releases, JQL.
• Sprint burndown chart that, unlike native charts, depicts remaining work and provides forecasts