How can a story be in more than one sprint

[Paul Carver]

We are using next-gen and have some stories that have somehow ended up in more than one sprint. Is this normal? Is there any way to prevent it?

I first have to say that I don't think the sprint based methodology is a good one for our project, but it is what our management wants us to do. We often have new work come in that can't wait a few weeks for the next sprint to start, so we add it to the current sprint and often have to move lower priority work to a later sprint.

I think it's as a result of moving items to a later sprint that some of our stories have ended up in multiple sprints. It doesn't happen all the time, some stories are successfully moved out of one sprint and into another, but due to something I don't understand, sometimes a story ends up retaining one or more old sprints rather than getting moved.

When I export issues to CSV I get a file with four sprint columns because we have two stories that have four sprints attached to them. We have a total of 47 stories with two or more sprints attached to them.

I would like to know how to remove all the extra sprints so that each story has only one sprint assigned and to prevent this from happening in the future.

[Alexey Matveev]

Hello,

If you finish a sprint with stories, which are not completed, those stories go to another sprint, but those stories still hold the finished sprint too.

[Paul Carver]

So does that mean I have to manually move every single story to the next sprint? This seems like broken behavior to me. But maybe it's just more evidence that the entire concept of sprinting all the time is just dumb.