Resolved stories moved into next sprint

[Deleted user]

We have an issue that I cannot seem to find the cause to.

We have stories that keep being moved into next sprints when closing sprint and starting a new one. This seems to happen even if the story has a resolution state such as: done, done done, won't fix etc. These are all marked as a resolved state (marked green).

Example: https://snipboard.io/euqOds.jpg

This story was marked as won't do in PL Sprint 4 but kept being moved along (we don't show won't do in our board filter)

[Nic Brough -Adaptavist- · Accepted solution]

The story was not "done" when you closed the sprint.

To be "done", a story must be in the last column on the board, along with all of its subtasks if it has any.

[Deleted user]

This could be it. Seems the stories had their status changed by editing the story and not by moving it to the left.

Is it possible to "fake" this on the stories that have the issue now in order to fix it without having to move them into a sprint and to the left-most column?

[Deleted user]

NVM, I just realised it. Thanks a lot for the help :)

[Deleted user]

Just in case anyone else run into the same issue; here is how it actually happened for us.

Stories were added to future sprints in the backlog, and then marked as duplicate or won't do. This resulted in them still being in that sprint, but not visible when we started it. Thus when we closed it, they were not correctly marked as resolved and moved on to next sprint.