Why did the completed points for a past Jira sprint change?
The Jira help pages give 4 common reasons. The first to rule out: Changing which statuses sit in which board column can change what the reports count as done.
Is it broken, or just quiet?
A number can fall because fewer people came, or because something stopped counting them. Below are the causes the Jira help pages give, and how to check each one yourself.
What causes it?
Changing which statuses sit in which board column can change what the reports count as done.
In the Jira help:
Board column configuration changes can cause discrepancy in the Reports.
How changing the Board column settings can impact the Sprint reports | Jira and Jira Service Management | Atlassian Support, read 2026-11-12.Sprint reports are worked out from the board as it is set up now, so a change today can alter the figures for a sprint that has ended.
In the Jira help:
The reports honour the Board settings(column, filter) as well as the issue history in real time.
How changing the Board column settings can impact the Sprint reports | Jira and Jira Service Management | Atlassian Support, read 2026-11-12.After a column change, work finished in one sprint can reappear in the next one with no points, which moves both sprints' figures.
In the Jira help:
The issues completed in the previous sprint will show up in the next sprint, with 0 story points.
How changing the Board column settings can impact the Sprint reports | Jira and Jira Service Management | Atlassian Support, read 2026-11-12.A burndown counts work by when it was done, not by which sprint it belonged to, so it can disagree with sprint figures.
In the Jira help:
Burndown reports are calculated at a point in time instead of relating directly to sprints or issues.
Burndown report shows different story points than other reports in Jira Cloud and Data Center, read 2026-11-12.
How do I check it myself?
Open the sprint's report and confirm that work still in progress is listed as not completed.
In the Jira help:
Check the Sprint report, confirm the issue in In Progress status is listed under the Issues Not Completed section.
How changing the Board column settings can impact the Sprint reports | Jira and Jira Service Management | Atlassian Support, read 2026-11-12.If you read completed points from a release burndown, check whether the board has more than one sprint running at once, since that makes the release burndown inaccurate.
In the Jira help:
Agile Boards containing multiple active Sprints lead to inaccurate information in Release Burndown report
Burndown report shows different story points than other reports in Jira Cloud and Data Center, read 2026-11-12.
How does Jira work with Feder?
- Connect Jira to Feder and it joins your Wins apps.
- When you connect Jira, Feder checks the connection straight away and shows Connected only when that check passes. If a reading cannot be taken later, Feder shows it as not read, never as zero.
Some numbers are too quiet to judge daily, such as a form filled in a few times a week. Until there is enough of your own history to judge a change, Feder says it is still learning and scores nothing, rather than guessing.
See whether you can trust the numbers in Jira, one of your Wins apps. Feder only reads. It never changes anything in Jira.
What else goes wrong with these numbers?
- Why are finished work items missing from my Jira reports?Jira
- Why did my resolved count in Jira suddenly jump?Jira
- Why did Google Analytics stop collecting data?Google Analytics
- Why aren't my key events showing in Google Analytics?Google Analytics
- Why does Google Analytics show (not set)?Google Analytics
See every question.
Where do these answers come from?
Every cause and check on this page comes from the Jira help pages, quoted above with the date we read them. Last reviewed 2026-11-12. We read them again by 2027-11-12. If one changes, this page changes or comes down.