Bulk changes moving stories to different Sprints

Irene Ali July 21, 2022

Hi Everyone,

When creating a bulk change to move stories into a different sprint, it creates a new Sprint number instead of moving it to the Sprint I enter.

Is there another step we are missing?

1 answer

1 accepted

0 votes
Answer accepted
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 21, 2022

Hello @Irene Ali 

Welcome to the community.

Are you work with issues in Company Managed project or a Team Managed Project?

Exactly how are you executing your Bulk Change? Are you using the Issue Search screen to find the issues to update? Which bulk change operation are you choosing? 

Or are you talking about the option when you are Completing a Sprint that allows you to move the incomplete issues to the Backlog or another Sprint?

Please provide more details about exactly what you are doing, the results, and how those results don't match your expectations.

Irene Ali July 22, 2022

 Hi @Trudy Claspill 

We have found the issue. In order to bulk move stories into a different Sprint, we need to enter the code # for the sprint in the "Change Sprint" section.

Screenshot 2022-07-22 232502.png

Screenshot 2022-07-22 232343.png

Thank you,

Irene Ali

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events