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

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?

1 answer

1 accepted

1 vote
Answer accepted

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.  

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

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

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Feb 26, 2019 in Jira Software

How to prevent the propagation of unused project schemes, workflows & screens in Jira software

Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...

590 views 0 6
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you