How to remove multiple sprints assigned to a story?

[Nicky Mano]

If we are closing any sprint and the open issues we will move either to backlog/Future sprints.

Here we are closing the Sprint1 and in progress story is moved to Sprint2. Since after its moved, we could able to see both the sprints tagged under the same story.

Is there any way to remove Sprint1 and keep only the assigned sprint as Sprint2.

[Bill Sheboy]

Hi @Nicky Mano -- Welcome to the Atlassian Community!

What problem are you trying to solve by doing this?

Removing the prior sprint values is trying to change the history of what happened, and so lose valuable information the team can use to learn about when/why issues did not finish when expected, and then consider how to improve in the future.

Kind regards,
Bill

[Robert McDonnell]

@Nicky ManoI would look at the following article.

https://jira.atlassian.com/browse/JRACLOUD-76173

The workaround listed actually worked for me.  The instructions are not super clearly written but in summary, you will go to a sprint report and pull the sprint ID # and then run a bulk action on the affected stories overwriting the sprint field with the ID number.  It will look wierd just seeing an integer but it should work.

You will need to make sure you over write the sprint field with a future sprint ID.  I tried the bulk action to clear out the value and that did not work on first try.  It only removed the current sprint, not the historical value.

Please let me know if this works for you.

[cynthiapaola.murillosalazar]

Hello, I have the exact same question.

We have a story that is assigned to 21 sprints, some sprints from over 2 years ago. The issue is that the current team has not worked on the story but it will be picked up and having these stories linked to so many sprints do not make sense for us now as the team and way of working has changed. So it would actually mess up our reporting to keep all the sprints

Does anyone know how to remove them?

[Bill Sheboy]

Hi @cynthiapaola.murillosalazar -- Welcome to the Atlassian Community!

Before changing any issues, I recommend pausing to understand how a Story could be assigned to 21 different sprints, perhaps using an RCA (root cause analysis) or retrospective discussion with the team(s) involved.

This symptom may indicate challenges with backlog refinement, product management, shifting goals, sprint planning, focus on the selected work, or perhaps Scrum is not a good fit for the type and method of requests the team implements, etc.

Understanding the cause may eliminate the need to alter the history stored in the Sprint field as the occurrence of multiple values in the field will be less frequent.

Kind regards,
Bill

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

You don't want to do this. 

It will destroy your sprint reports, and make it pointless to do sprints.