Troubleshooting and FAQ

Check the following:

• Is Sprint Autopilot enabled for this board? Open Sprint Autopilot from the ... menu and confirm the Enable Sprint Autopilot toggle is ON.

• Is there already an active sprint? Auto-start only fires when no sprint is currently active. Complete or close the active sprint first.

• Is the sprint in future state? Auto-start only applies to future sprints. If the sprint is already active, nothing happens.

• Is the start date in the past? The scheduler checks every 5 minutes. Allow up to 5 minutes after the start time.

Check the following:

• Is Auto-close enabled? Open Sprint Autopilot and confirm the Auto-close toggle is ON.

• Is the sprint active? Auto-close only applies to active sprints. A future sprint will not be closed.

• Has the end time passed? Allow up to 5 minutes after the end time for the scheduler to run.

This happens when auto-create runs while a sprint with the same incremented name already exists. From version 2.3.0, auto-create is skipped if any future sprint already exists on the board, which prevents this. If you see duplicates from earlier runs, delete them manually in the backlog.

You need the Manage Sprints project permission to save sprint details. Contact your Jira project administrator to grant this permission.

Sprint Autopilot only works with Scrum boards. If you are on a Kanban board, the option will not appear. If you are on a Scrum board and still do not see it, confirm the app is installed and that the installation completed successfully.

Yes. Settings are stored per board, not per project. Each board can have its own autopilot configuration independently.