Had an issue in a sprint that: * was initially un-estimated as far as story points were concerned. * was given an estimate during the sprint (allocated a 3). * was subsequently closed near the end of the sprint. * was attributed to a version after closure (i.e. the fix version wasn't set initially either). The problem is that the 3 points aren't being added to the sprint velocity for number of points completed in the sprint. Ideas why?

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Story points for issue in sprint not added to sprint velocity when issue closed. Why?

unknown

Had an issue in a sprint that:

was initially un-estimated as far as story points were concerned.
was given an estimate during the sprint (allocated a 3).
was subsequently closed near the end of the sprint.
was attributed to a version after closure (i.e. the fix version wasn't set initially either).

The problem is that the 3 points aren't being added to the sprint velocity for number of points completed in the sprint. Ideas why?

Accepted answers

Ivar

JIRA Agile says so when you start the sprint - if there is an unestimated issue when you start the sprint, any estimates on this issue later on will not be added.

In order to include it in the total number of points for the sprint, you would have to remove the issue from the sprint and then add it again.

I assume the reason behind this is to provide a decent metric on scope change, e.g. scope creep.

All comments

Ivar

JIRA Agile says so when you start the sprint - if there is an unestimated issue when you start the sprint, any estimates on this issue later on will not be added.

In order to include it in the total number of points for the sprint, you would have to remove the issue from the sprint and then add it again.

I assume the reason behind this is to provide a decent metric on scope change, e.g. scope creep.

unknown

thanks for the info - helps a lot. Yes, trying to make our metrics real and meaningful.

unknown

Can I do the remove and add to the sprint after the sprint has been closed?

Ivar

I believe the answer can be found here: https://answers.atlassian.com/questions/141766