Velocity/sprint chart doesn't show updated ticket status

Question

What happens if you close a ticket as DONE by mistake, COMPLETE the sprint, and then realise your ticket wasn't done so you reset it as IN PROGRESS?

What seems to happen is that the velocity chart from the previous sprint doesn't update. That means potentially you are double counting the same ticket twice. Surely that is a bug?

I find it particularly troublesome if you look at the Sprint report and you see a ticket number, ticket description and status, with the status NOT being the current status (I.e. from this view it looks DONE, whereas when you click on it, you can see it is IN PROGRESS).

I am confident it didn't use to behave like this, so why did you change it?

Ste Wright · Answer

You are choosing to reopen the Story though, re-add it to a Sprint, and complete it twice. It's counted twice as it was incorrectly closed then reopened.

The Sprint Report, and Velocity Chart, are factually correct - within the specific Sprint you did complete that issue, whether by accident or not.

---

I assume there's no simple method to modify the results as this would also be counterproductive - it would make it possible to manually manipulate the data.

That being said, you could try...

* Reopening the Sprint, moving the issue out of Done, and re-closing it
* Removing the issue from the Sprint (after reopening it)
* Bulk editing the Sprint field (to clear it completely)

...and see if this has an impact on either report?

Ste

l bascle · Answer

The eternal question: bug or feature.

It may be by design, but if we think of the essence of a velocity chart, which is to measure a team's ability to absorb and output work, then it doesn't make sense. You need to be able to know what was truly completed in each sprint. The feature should be able to cater for errors and corrections, which is the specific case scenario I am discussing here. If a ticket is counted twice, it completely defeats the point of a velocity chart.

Ste Wright · Answer

Hi @l bascle

Isn't this the correct behaviour?

The issue was completed in the original Sprint - even if it's reopened. The report is point-in-time, rather than reacting to what happens after its closure.

You're then choosing to reopen it - but this does not take away from the fact that the issue was "completed" in the original Sprint.

Ste