UAT complete should not reflect as Spillover

[Chaitanya Gandhi]

I have created a workflow where I have marked that UAT complete as a Done state. I did this as we do releases on Monday and I want to close a Sprint on Friday and not treat them as spillover just because we did not release on a friday night.

I was of an assumption that making UAT complete state as done in workflow would resolve this issue and lead to accurate reporting but I was wrong and all these stories were spilled over and my velocity of Sprint is shown as 0. 

Anyone can help me with a workaround or how they handle this issue as only release might go to next week. 

[Nic Brough -Adaptavist- · Accepted solution]

Is the "UAT Complete" status in the last column on the board?

[Chaitanya Gandhi]

No it is not. So is it that JIRA identifies based on last column and not the category of status?
My last column is released and I have kept it so that I know what is released within the sprint if any.

Is there some workaround?

[Nic Brough -Adaptavist-]

Correct.  The last column on the board is "done".  The others are not done, so they will carry over to the next sprint when you close the sprint.

The "workarounds" are:

• to define a proper binary "done" status and use it appropriately
• to put your released status into the "done" column (assumes you are using classic projects, not Next-gen)

[Chaitanya Gandhi]

Got you.. Thanks...