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).
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)
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?
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.
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