Sprint Automation: Auto Start, Close & Create Sprints
Sprint Autopilot for Jira automates the sprint lifecycle for every board, with no admin dependency. Run it from the Apps console, or open it from the ... menu on any sprint card.
What this app does
Configure once per board. The scheduler checks every 5 minutes and handles the sprint lifecycle based on the exact start and end date and time set on each sprint.
Sprint editor - edit sprint name, duration (1 to 4 weeks or custom), start date and time, end date and time, and sprint goal in one place.
Auto-start - starts the next future sprint when its start date and time arrive and no sprint is currently active.
Auto-close - closes the active sprint when its end date and time pass.
Auto-create - keeps future sprints ready ahead of time. Choose how many to keep queued, up to five, each with the same duration and an incremented name.
Roll over unresolved work - on close, moves open issues to the next sprint or to the backlog, your choice.
Skip empty sprints - optionally skip sprints that have no issues or no dates, so placeholder sprints never launch by accident.
Board aware - correctly handles projects with multiple Scrum boards and parallel sprints.
Per-board config - each board keeps its own autopilot settings.
Where the app lives
Surface | How to open |
|---|---|
Apps console | Top navigation - Apps menu - Sprint Autopilot. Lists every Scrum board with its status, active sprint, last action, settings and audit trail. |
Sprint card panel | Backlog - click ... on any sprint card - select Sprint Autopilot |
Changing a board's automation needs the Manage Sprints permission on that project, the same permission required to start or close a sprint by hand. Without it, the settings show as read-only.
Built on Atlassian Forge. All data stays inside your Atlassian tenant. No external servers and no external databases.