Admins and the project manager manage sprints from the board's Backlog tab.
Create a sprint
| Field | Required | Details |
|---|---|---|
| Name | Required | For example, Sprint 1. |
| Goal | Optional | What the sprint should achieve. It's shown in the sprint header. |
| Start Date | Required | Must be on or before the end date. |
| End Date | Required | Must be on or after the start date. |
Date rules
- A sprint's dates must fall within the project's start and end dates.
- Sprints on the same board can't overlap. If they would, Atlas suggests dates that fit.
- Every ticket's due date must fall inside its sprint's dates.
New sprints start as Planned.
Start a sprint
Select Start on a planned sprint. Only one sprint can be active on a board at a time, so complete the current sprint first. Starting a sprint notifies the project team.
Edit a sprint
Open Edit Sprint, choose an active or planned sprint, and update its details. Completed sprints can't be edited. If someone else changed the sprint while you were editing, Atlas warns you instead of overwriting their changes. Closing with unsaved changes asks "Discard unsaved changes?".
Complete a sprint
- 1
Select Complete Sprint
- 2
Decide what happens to unfinished work
Turn on Return incomplete tickets to backlog to move tickets that aren't in the completion stage to the end of the backlog. Finished tickets are then cleared from the sprint as well.
Leave it off to keep every ticket attached to the completed sprint.
- 3
Confirm
The sprint becomes Completed and the project team is notified.
Sprint statuses
| Status | Meaning |
|---|---|
| Planned | Created, not started. Tickets can be planned into it. |
| Active | Running. Its tickets appear on the Board tab. One per board. |
| Completed | Finished. Read-only. |