We are not clear on how it is calculated and cannot find it in help
Hi @Lucy Olson -- Welcome to the Atlassian Community!
Reviewing the information for the Sprint Report and the Velocity Report...
https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-sprint-report/
https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-velocity-chart/
You will find what Atlassian calls "commitment" is the total of the estimate measure (e.g., Story Points) for the issues in the sprint at the time the sprint started.
Any changes to issues in the sprint, or changes to the story points for those issues, are not in the total. Instead they are considered scope change / changes to forecasts.
Kind regards,
Bill
Hi @Lucy Olson
Welcome to the community!
In your shared data you have mentioned 44 points are "not completed" and 24 as removed, but were any of the issues from these 2 sets added after sprint start? Because if they were added after sprint start and later removed or left incomplete then they won't count towards the "committed" total of 139.
Also, with my SaaSJet team, we built a new Sprint Performance Report where we have all the metrics for each sprint. One of them is committed.
You can also book a live demo - we'll show you the application inside out and answer all your questions.
Happy Sprinting 🥳
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.