Overview
Sprints are timeboxed batches of work on projects that use the Scrum style. A sprint has a name, a goal, and start and end dates. On the project's Tasks view, tasks live either in a sprint or in the backlog, and sprints move through a simple lifecycle: planned, active, then completed.
Who can do this
- Required access: an access level that includes Tasks - Full Access.
- Default access levels that include it: Accountant and System Administrator.
- Owners and admins: always allowed. Workspace owners and admins are not limited by access levels.
- You also need access to the project the sprint belongs to.
- Personal accounts: The Family Admin preset includes this access. The space owner and admins can always do it.
Owners and admins review and change access levels in Settings → Administration → Members → Access levels.
Before you start
- Sprints appear on projects created with the Scrum project type. Other project types use task groups instead.
- Creating and managing sprints needs Tasks - Full Access and access to the project.
Create a sprint
- Open your project and go to its Tasks view.
- In the filter bar, use the add button and choose Sprint.
- In the New Sprint dialog, give the sprint a name, an optional goal, and start and end dates. The end date must be after the start date.
- Click Create sprint. It appears in the Upcoming section as a planned sprint.
Add tasks by dragging
The fastest way to fill a sprint is dragging rows onto it:
- Select one or more task rows in the backlog (or in another sprint) using the row checkboxes.
- Drag the selection onto the target sprint's card. The card highlights and shows how many tasks will move — drop to move them all at once.
- To pull work out of a sprint, drag rows onto the Backlog section instead.
You can also set the sprint from a task's sprint field, or filter with the query bar using sprint = "Sprint 12".
Run the sprint
- When the team is ready, click Start sprint on the sprint. It moves to the Current section.
- Work the sprint as usual — statuses, assignees, and estimates all update live.
- At the end of the timebox, click Complete sprint. If tasks are still incomplete, choose what happens to them: move them to the backlog or roll them into the next sprint.
Best practice: Set story points on tasks before starting the sprint. Points make sprint progress and planning history meaningful.
Troubleshooting
| Issue | What to check |
|---|---|
| No sprint options on the project. | The project is not a Scrum project — sprints only appear on the Scrum project type. |
| The sprint card does not highlight while dragging. | You cannot drop tasks onto the sprint they already belong to; drag to a different sprint or the backlog. |
| You started a sprint too early. | Use the sprint's menu to move it back to planned. |
Next steps
- Review team throughput in a workstream's Flow panel.
- Structure non-Scrum projects with task groups instead.