Hi @Bar Benezri and welcome to the Community!
Not that I do not want to dive into a technical solution for what you are asking for, but your requirement does not seem to make much sense at first sight (sorry for that candid feedback).
When you choose to run sprints to plan your work, you do so because you want to take control over the items you are putting into the hands of your development team. You want to evaluate how the team is doing and actively discuss which items you are going to do next, evaluate if they are ready to be picked up, discuss why certain items were not completed and see where you can improve.
Automatically closing your sprint every week and automatically starting a new sprint with the items that were not completed before eliminates everything that way of working was designed for.
So if you don't do all this planning work or evaluation with the team at the end of the sprint, creating weekly sprints just creates overhead. Which then leads to the desire to automate that overhead out of the way again.
Having said that, it seems at first sight that using a kanban board with a kanban backlog would be a better fit for the current way your team is working. You won't need to create and close sprints anymore every week, neither manually nor in an automated way. All you would need to do is move items from the backlog onto the actual development board at the right time.
Maybe you are currently using your sprint as a way to organise work that needs to be completed as a whole, somewhat like an MVP. If that is the case, eliminating your sprints may initially seem like a loss for organising your work, but using fixversions (releases) would be a better solution if that's what you really need to be able to do.
I know it's not a direct answer to your question, but hopefully a better solution for the problem you're trying to solve. Hope it helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.