HI community ,
I have a task with 5 story points which in the middle of the sprint was decided to move to done with won't do resolutions status.
Will it be counted in velocity completed points or do I need to reeastimate it to 0 not to have wrong velocity?
Thanks in advance .
You say "resolution status" - resolution and status are two very different things. Which one do you mean here?
I'm going to guess resolution, in which case, you've done the right thing - your task will be shown as done, you've put it in the last column on the board which tells Jira it is "done", so it will be counted in the burn down - you've completed a 5 point story in the sprint.
So, yes, it might look a bit odd to say you've done this story when you did little work on it beyond talking about why you don't need it any more, but in most cases, it will be better to leave it with the 5 points and let it count towards the burn down.
If you set it to 0, then yes, you're recognising it was no effort (but, Story points are not effort or time measures), but you're also changing the scope of the sprint. The 0 setting will not change what you committed to at the start of the sprint, and your velocity will look wrong because you're no longer measuring it against committment.
I mean when I move the task to done column , it offers to chose " Done " "Cannot reproduce "and "Wont do " . In fact it's status is Done , but it is not.
Regarding the scope and velocity, in reality we inspect the changes issues in during the sprint and if necessary adapt accordingly adding tasks or reviewing the implementation of the ones we have in sprint. So the only concern whether I have to change to 0 th estimate of wont do task. Just checked in my report that it its important to changed the estimate to to have that points calculated as completed.
I need to be clear on this, to avoid talking about the wrong thing:
You say "When I move the task to done column it offers [3 options]"To me, this is unclear which one of these two things it is doing:
Either way though, I cannot recommend you set the estimate to 0, you're destroying the fact you estimated at all, warping the sprint statistics and changing the scope of the sprint. I recommend leaving it and accepting that 5 points was a good estimate but someone decided not to do it.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events