How to handle canceled issues

[Orit Nachshon]

Hi,

I'm struggling with the right way to handle canceled issues in the sprint.
I tried several options, but didn't find a way that will reflect the truth.
1. If I put the canceled status in a mapped column, or the un-mapped, then the reports are fine (velocity, burn down, sprint report), but at the end of the sprint the issue will be transferred to the next sprint or back to backlog.
2. If I am removing the canceled issues from the sprint, then the burn down report doesn't count them as committed.

3. If I am filtering out the canceled issues from the board's filter - again the reports are not taking them into account.

How are you handling it?

Will be glad to hear some ideas.

Thanks,
Orit.

[Ollie Guan]

Hi @Orit Nachshon,

You can try matching the Status=Canceled to the Done column in the Board configuration.

When the user moves the card, please pay attention to the final state.

[Orit Nachshon]

 Thanks for your answer. The solution is a bit risky, no? Canceling issues by mistake?

[UKSecurityEngineering]

How can i place cancelled within the done column?  I have it set in column management, and have cancelled in "set resolution" But refreshing the kanban board, it still resides in separate column.

Orit, you can move them out of cancelled if you place them in the wrong box. I haven't set up the boxes for that column, but i've used them. So you can definitely move them into the done box instead of cancelled if you made a mistake. Just ensure it's in the right one before you release.

[DSell]

@Ollie Guan So how did you get Done to appear on top of Cancelled? Mine shows Cancelled at the top which is even more dangerous