Release Burndown report shows total Story Points mismatch
The Release Burndown report shows a total of Story Points for a specific closed sprint that is higher than the sum of the story points of the issues on that sprint.
- The Story Points total is higher than the sum of the story points of issues on that sprint shown.
- The sprint is closed and it is not the most recent sprint.
- An issue closed during that sprint was removed from the Version.
According to the documentation: Viewing the Release Burndown
Issue completed in a version, but removed from the version afterwards:
- The scope will remain unchanged and the work completed is still show
The Release Burndown allows you to add and remove issues from the version (by changing the "Fix Versions") for issues worked on the last sprint. Once a newer sprint has been closed, the Sprint Story Points are fixed and the above rule applies: "The scope will remain unchanged if issues are removed from the version."
- An issue closed during the duration of that sprint was added and removed from the Version.
If you add an issue to the version, it will add the story points to the scope of the sprint that was active when the issue was resolved:
If the issue is removed again from the Version, the story points will still be counted in the total.
Issue completed in a sprint, but only added to the version afterwards:
- The issue will be shown on the report, as if it was always part of the version.
To investigate what happened:
- Open the Burndown Chart for the given sprint to see if there are more issues listed in the sprint that they are listed in the Release Burndown.
Search for issues that were removed from the version using JQL:
project = <PKEY> and (fixVersion not in ("<version>") or fixVersion is EMPTY) and fixVersion was in ("<version>") order by resolved desc