Issues Not Automatically Moved to Next Sprint After Sprint Completion

[Minju Kim]

Dear Atlassian Support Team,

I hope this message finds you well.

We recently completed a sprint in our Jira board and selected the option “Move incomplete issues to the next sprint.” However, we noticed that many of the incomplete issues were not moved to the next sprint, and instead, they were sent back to the backlog.

Could you please help us understand why this might have occurred?

• Are there known limitations or conditions that might prevent issues from moving automatically?

• Is there a way to review the transition logs for this sprint?

• Is it possible to recover those issues into the current sprint in bulk?

Our team relies heavily on this feature for our sprint planning process, so we’d appreciate your guidance on resolving this issue.

Thank you in advance for your support.

Best regards,
Minju Kim

[Sanam Malleswari]

Hi @Minju Kim

It seems like there might be a few reasons why incomplete issues weren’t moved to the next sprint:

1. Board Configuration: Ensure your board allows automatic movement of issues after sprint completion.

2. Issue Status: Check if any issues are marked as “Done” or have a status preventing them from being moved.

3. Sprint Settings: Double-check that the “Move incomplete issues” option is selected correctly.

4. Transition Logs: Review the Issue History for details on what happened during the sprint completion.

5. Bulk Recovery: You can use Bulk Change to move issues back to the current sprint if needed.