Closing Sprint - move issues to the top of the next sprint

Question

I have a bit of an unusual setup regarding sprints, since we are working with a supplier and they need us to plan a few sprints ahead. What we also agreed on is, if any work that was already ordered (starting a sprint with new tickets is ordering them) they will automatically move to the next sprint.

All good so far - but what bugs me quite a bit is, that when moving issues to another sprint, they are not added at the top of the sprint backlog but at the bottom. Usually old or unfinished stories have a higher priority (otherwise they would have been further back in the product backlog).

So - without any regards of this is the right or wrong way to plan - is there anyway I can tell JIRA to move unfinished issues when closing a sprint to the top of the sprint backlog?

If yes, pls explain - if no, well nevermind, I'm creative I'm sure I'll finde a solution :-)

Marina Triebe-Gravel_gfk3rn · Answer

I'm having the same issue as the OP in 2024. We use rank and "physical" ticket order to plan the sprint. As I move tickets from one sprint to the next, they always go to the bottom of the new sprint, no matter the rank. Like the OP my team pulls tickets from the top of the sprint. Is there a way to send tickets from one sprint to another to the top vs the bottom?

Bill Sheboy · Answer

Hi, Maria.  If this solution works for you, please mark the answer as accepted so others can benefit from it.

Thanks!

Maria Hauer · Answer

Hi @Bill Sheboy ,

ahhh...that might be the reason, since I'm putting new issues directly into the pre-created sprint they are not ranked properly looking at the "big" picture.

I'll try that, many thanks!

Cheers, Maria