A few questions regarding the Velocity Chart report logic

Ray Johnson DISH

This is question for Jira Data Center and Server 8.2. Does anyone definitively know the answers to these Velocity Chart report logic questions?

1. If a story/points are pulled into a sprint after sprint start, are the points committed?

2. If the sprint starts without any stories/points, are there 0 points committed? Will pulling in a story after sprint start commit points to it?

3. If a story/points are completed after sprint end, which sprint will the points be counted?

4. If points are counted in a past or closed sprint, will that reflect in the velocity report immediately?

5. What status must the story/points be in to be "completed" at sprint end: Done or Accepted? 

Trudy P Claspill

Hello @Ray Johnson DISH 

Welcome to the Atlassian community.

1 & 2:

The Committed Points in the Velocity Chart are set at the moment the sprint is started. The value is not impacted by changes after the sprint is started, whether those change include removing/adding issues to the sprint or changing the Story Points allocated to the issues already in the sprint.

3. Story points are added to the Completed value only if the story is completed within a sprint. If the story is completed after the sprint is ended, and the story is not in another active sprint, then I believe the story points are not counted in the Completed metric for any sprint in the Velocity chart.

4. I'm not sure what you are asking in this question. Do you mean if you change the story point value for an issue that is already completed and counted in a past sprint in the chart? Changing story point values in issues does not impact the Velocity Chart report for sprints that are already completed.

5. The issues must be in the status mapped to the column farthest to the right on your Scrum board where you manage those sprints. It doesn't matter what the status actually is. It only matters that the status is in the right-most column.