Settings Reference
All settings are per board. Manage them from the Apps console (top navigation - Apps - Sprint Autopilot) or from the ... menu on any sprint card. Changes take effect on the next scheduler check, which runs every 5 minutes.
Changing these settings needs the Manage Sprints permission on the board's project, the same permission required to start or close a sprint by hand. Without it, the settings show as read-only.
Sprint Autopilot settings
All automations are inactive unless Enable Sprint Autopilot is ON.
Setting | Description | Default |
|---|---|---|
Enable Sprint Autopilot | Master switch. Turns all automations on or off for this board. | OFF |
Auto-start | Starts the next future sprint when its start date and time arrive and no sprint is currently active on the board. If multiple future sprints exist, the one with the earliest start date is started. | ON (when autopilot enabled) |
Auto-close | Closes the active sprint when its end date and time pass. Unresolved issues are routed according to the Roll over unresolved work items setting. | ON (when autopilot enabled) |
Auto-create count | How many future sprints to keep ready ahead of time, from 0 to 5. The app tops up to this number after a sprint closes and when the queue runs short. Each new sprint copies the previous duration and uses an incremented name. At 0, a single next sprint is still created only when one is needed to receive rolled-over work. | 1 |
Roll over unresolved work items | Where to move issues that are not in Done status when the sprint closes. | Move to next sprint |
Skip empty sprints | When ON, the app skips sprints that have no issues or no dates instead of auto-starting them, so a placeholder sprint never launches by accident. | OFF |
Last action and audit trail
Both surfaces show the most recent automated action for the board: what happened, which sprint, and when. Examples:
Auto-started "Sprint 3" on May 25, 2026 at 9:00 AM
Auto-closed "Sprint 3" on May 31, 2026 at 9:00 AM, moved 3 issues to Sprint 4
Auto-created "Sprint 4" on May 31, 2026 at 9:01 AM
The Apps console keeps the full history per board on its History tab, which you can export to CSV or JSON.
Editing sprint details
The sprint card panel lets you edit sprint details directly from inside Jira without opening the sprint settings dialog: sprint name, duration, start date and time, end date and time, and sprint goal. See Editing Sprint Details for full detail.