Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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:

5 answers

1 accepted

0 votes
Answer accepted

Answered above

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

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.

Thanks Rahul - that's really helpful.  I'll give that a try next time I need to do this.

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.

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

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

Like Christophe 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? 

Like Aneesh Joshi likes this

Did you ever find a resolution for this issue @haleyeberly ? I have the same problem. 

Like # people like this

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Agile

Join us LIVE: Atlassian & Experts Talk Research & Insights @ Scale

Hello all! What have you learned from your customers lately? Our live-streamed series continues by exploring CX, UX, and the power of research & insights at scale with Leisa Reichelt, Head of R...

270 views 3 6
Read article

Community Events

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

Events near you