Discrepancies between Velocity Report's commitment and the Sprint report's sum of Story points at the start of the sprint
Platform Notice: Cloud - This article applies to Atlassian products on the cloud platform.
Summary
The Sum of Story Points at the start of a Sprint is not equal & is greater than the total Story Points shown as "Commitment" in the Velocity Chart report in a Company Managed Project.
Environment
For Cloud Only
Diagnosis
The Commitment value of the respective Sprint in the Velocity Chart does not include Story Points from issues which have been cancelled before the start date of the Sprint. So there might be issues that were included in the Sprint before the start of the Sprint, but they were moved to a status that signals that the issues will not be worked upon like Cancelled, Won't Do etc and they were moved to these statuses before the Sprint was started.
Cause
Please note that the Sprint commitment is the sum total of estimations (as of the sprint start date) for all issues that:
- were added to the sprint prior to the sprint’s start date
- are not in an unmapped status in the respective board(they will be included in Sprint but count as 0 estimation in Velocity report)
- are part of the Sprint but they are not yet complete or have been cancelled before the start date of the Sprint.
Therefore, those issues that do not follow the above logic/design, are excluded from the Commitment calculation.
Please note that the implementation of Velocity report is different in the Jira Server instance as compared to Jira Cloud. The above explanation applies only for Cloud instance.
Solution
If you see that the Story Points of any issue is missing from the list of issues included in the Commitment calculation of the Velocity report, then please go to the "Issue History" section of that issue and ensure the below:
- Ensure that the issues was added to the Sprint before the sprint’s start date.
- Ensure that the status, on which the issue is on currently, is not an unmapped status in the respective board(they will be included in Sprint but count as 0 estimation in Velocity report).
- Ensure that the issue has not been moved to a status like "Cancelled", "Won't Do" (Done Category statuses) before the Start Date of the Sprint, as they will be considered to be incomplete or cancelled before the Sprint starts and hence will not be included in the Commitment calculation.