Sprint Automation for Jira Cloud starts, closes, and rolls over your sprints automatically, on the schedule you set. Plan a sprint’s start and end dates once and the app opens and closes it at exactly those times — no more manual sprint management or sprints left running over a weekend.
1. Open the configuration
From Jira’s left sidebar, go to Apps → Sprint automation configuration (it opens under your Jira admin settings). You’ll land on the Initial configuration screen below.
- Select scrum boards — choose the boards whose sprints should be automated. Only the boards you pick here are touched.
- Handling of incomplete issues — decide what happens to unfinished work when a sprint closes (for example, roll it into the next sprint).
- Save — apply your selection. From now on, changing a sprint’s dates schedules its automatic start and close.
- Sprint Date Configuration Help — use Jira Automation smart values to set precise start/end times (e.g.
{{now.plusWeeks(2)}}), so timing is exact even when processing runs after configuration.
2. Run Sprint Automation
- Select the boards on which you want to automate starting and closing of sprints.
- Go to those boards and plan your sprints, setting a Start date and End date on each.
- That’s it — Sprint Automation will start and close each planned sprint at the times you set.
Warning: if you plan overlapping sprints (the start of one is before the end of the previous), the running sprint closes automatically when the new sprint starts, ignoring the overlapped sprint’s end date. Leave at least one minute between sprints to avoid this.
3. Test it safely
Do not test on an existing project — automation can affect metrics such as velocity and completion ratio. Create a new project with a Scrum board and test there:
- Create a sprint.
- Set a Start date in the near future or the past. If it’s in the past, the sprint starts immediately; if it’s in the future, it starts at that date and time.
- Set an End date and confirm the sprint closes on schedule.
Application logs
Use the Sprint Automation Logs page (Apps → Sprint Automation Logs) to confirm each scheduled start and close ran as expected and to troubleshoot timing.
Need help?
Questions or feature requests? Reach the Divim team through our Help Center, or view the listing on the Atlassian Marketplace.