How can Jira automatically move tickets to next sprint?

[shelly]

We have about 10 developers and each has about 15-20 tickets (open, in progress, on hold) that will need to be moved to the next sprint by every Monday morning 6am. 

how can we accomplish this without having to manually move them?  

[Mirek]

HI @shelly ,

Congratulations on your first post on Community!

If you end the sprint by default all unresolved issues should be moved to a next sprint or backlog. Since Jira 7.12 (if using server version) it is possible also to create a new sprint when closing the sprint so even more options. 

[shelly]

we cannot end the sprint because they the sprint field accumulates in each ticket which we don't like. 

what we typically do is that we manage several tickets that are not going to be completed before Monday starts, therefore the manager manually does a bulk update on a sunday night before the developers come into work Monday morning and moves it to the next sprint.  Then closes the previous sprint so that field doesn't get accumulated with sprints.

is there a better way?

[Nic Brough -Adaptavist-]

Oh, that's not good.  The best way to do this is use sprints properly - close them when they are done.  If you've got issues going through many sprints, then they're sized incorrectly and should be moved to Epics, then broken down into stories that do fit into sprints.