JIRA issues going to backlog instead of next sprint


Our issues used to roll into the next sprint when the current sprint is ended. Now, however, they go to the top of the backlog instead of rolling over, and we end up having to search for issues in the prior sprint where resolved is empty in order to bulk-change them to the new sprint.

We don't recall changing anything but ... clearly something did! Any hints are appreciated, thanks!

We're on Server edition 6.4.11.


1 answer

This widget could not be displayed.

Thanks, Arun!

I started with that AAQ thread yesterday, but alas, it doesn't address the fact that sometimes issues roll over into the next sprint and sometimes they don't, which is why I posted this new question.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

157 views 1 3
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you