How can you remove issues from a sprint in bulk?

You can remove issues from an active sprint by changing the sprint field to empty. You do this by leaving it blank but checking the update box.

You'll see this message on your confirmation page:

6 answers

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

1 vote

Answer accepted

Answered above

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

2 votes

Hello Mark,

You will need to create a filter and exclude the Sub-tasks, and then try changing the Sprint.

It worked for me, as the Sub-tasks will anyways inherit the Sprint name from the parent tasks - safe and sound.

Regards,

Rahul

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

2 votes

Hmmm, it doesn't seem to let you do this any more. I really need to be able to edit the closed sprints associated with a number of issues that have moved between teams/boards as this has caused the velocity charts to break.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

0 votes

It is Aug 2022 and this is still working! Yay!

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

0 votes

Leaving the field blank not only removed the current sprint but all sprints that were in that field. Meaning if you had tickets that rolled from sprint to sprint it would delete the previous sprints as well.

For me, this made a large difference it what I actually wanted to update.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Experienced this as well. Not an ideal default functionality for Bulk change.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like • Joel Young likes this

Same here....
We also have strange behavior, when "done" issues are rolling from closed sprint to the new sprint...
At the moment, seems like we will need to manually remove the new sprint from them

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like • Christophe Ligniert likes this

I"m experiencing the same issue above where closed/deployed issues are inheriting sprints even after being in DONE status. This is causing my velocity charts to break. Was anyone able to figure this out?