User Guide
Two ways in
All settings are per board. You can manage them from either surface:
Surface | How to open | Best for |
|---|---|---|
Apps console | Top navigation - Apps menu - Sprint Autopilot. | Seeing and configuring every Scrum board from one page, plus the audit trail. |
Sprint card panel | Backlog - ... menu on a sprint card - Sprint Autopilot. | Editing one sprint and that board's settings while you plan. |
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.
Apps console
The console lists every Scrum board the app can see. For each board it shows the on or off status, the current active sprint, and the most recent automated action. Open a board to:
Settings - turn autopilot on or off and set the per-board options below.
History - the full audit trail of automated actions for that board, exportable to CSV or JSON.
Sprint editor
Available from the sprint card panel.
Field | What it does |
|---|---|
Sprint name | Rename the active or future sprint. |
Duration | Custom or 1 to 4 weeks. Selecting a week count auto-calculates and locks the end date from the start date. |
Start date and time | When the sprint starts. Used by auto-start. |
End date and time | When the sprint ends. Used by auto-close. |
Sprint goal | Add or update the goal text. |
Autopilot settings
Setting | What it does |
|---|---|
Enable Sprint Autopilot | Master on/off per board. Disabling stops all automation without clearing settings. |
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 queued ahead of time. Set how many to keep ready, from 0 to 5. Each new sprint copies the duration and uses an incremented name. |
Roll over unresolved work items | On close, moves issues that are not Done to the next sprint, or to the project backlog. |
Skip empty sprints | Optional. Skips sprints that have no issues or no dates, so a placeholder sprint never auto-starts. |
Last action and audit trail
Both surfaces show the most recent automated action for the board: what happened, which sprint, and when. The console History tab keeps the complete record, which you can export to CSV or JSON. The app checks idempotency on the last action so it never double-fires on the same sprint.
The scheduler runs every 5 minutes. Auto-start and auto-close fire based on the exact date and time configured on each sprint. Boards are processed in parallel batches with retry on transient errors.