nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Closing Sprint donot move incomplete tickets to New Sprint.

Sanjog Sigdel

Ideally Closing a sprint should move all incomplete tickets to either next sprint or the filed that we choose.
Every time I close the sprint, I select the option to move the tickets to the next sprint. But most of the tickets are not moved to the next sprint and the sprint is unassigned.

Is anyone in the community facing the same issue? I need to resolve this. Can I as a Jira Administrator configure this behavior somewhere on my own before I reach out to the Atlassian support?

Accepted answers

TC Wang_f5xqx2

Hi @Sanjog Sigdel I would check the following:

* Check whether tickets are in the same project/sprint. Can use filters/adv. issue searches to further check.

* Check whether tickets have statuses that are mapped to the rightmost column of the board (considered done by Jira and won't be moved).

* Check the parent-child relationships of the tickets. Could be the case that subtasks are already in the next sprint but parent tickets are still in the current sprint.

I also found this doc. See if Using Manage Sprints permission for advanced cases at the bottom suits your needs.

Hope the above helps!

All comments

TC Wang_f5xqx2

Sanjog Sigdel

Thanks @TC Wang I'll give this a try.

TC Wang_f5xqx2

Hey @Sanjog Sigdel just curious - has the issue been resolved or have you found anything during checking?