A sprint is a short working cycle inside a project. It helps collect the next period of work, keep it separate from the broader task flow, and show how much is done, how much remains, and what outcome the team is aiming for.
In short: enable sprints directly on the sprints screen or in project settings, create a planned sprint, add tasks from backlog and active work, then start it. A project can have only one active sprint at a time.
1. Enable sprints for a project
If sprints are not enabled for any project yet, you can enable them with one click directly on the Menu → Sprints screen — select a project and press the enable button. You can also turn them on in project settings: open Menu → Administration → Projects, choose the project, and turn on the Sprints toggle. The project then appears on the sprints screen, and the task form can offer sprint selection.
Project settings and sprint activation are managed by the workspace owner and admins. Regular members work with tasks in the projects they have access to.
2. Create a sprint
- Open Menu → Sprints.
- Select a project if the workspace has several projects with sprints enabled.
- Press Create sprint.
- Enter a clear name, goal, start date, and end date.
- Add tasks before saving, or create an empty plan and fill it later.
Keep the name short and recognizable, for example “Sprint 12: Launch Readiness”. The goal should describe the outcome of the sprint, not just repeat the task list.
3. Fill it with tasks
Add tasks opens the project task picker. It has two tabs: Backlog for deferred tasks and In progress for tasks already in active statuses. Search helps find the right card by title.
Sprints contain root tasks from the project. Subtasks follow their parent task and are not selected separately. If a task already belongs to another sprint, it is shown as unavailable so the team plan stays clear.
Backlog tasks stay in backlog while the sprint is planned. When the sprint starts, iTasks gives the New status only to tasks in that sprint that are in the backlog and not linked to a workflow. Tasks linked to a workflow keep their stage and status.
4. Start the sprint
Open the planned sprint details screen and press Start. After confirmation, the sprint becomes active, and only its backlog tasks that are not linked to a workflow receive the New status. Tasks linked to a workflow keep their stage and status. If the project already has an active sprint, a new one cannot start until the current sprint is closed.
The sprint card shows the goal, creator, dates, task list, and counters for Total, Done, and Remaining. Selecting a task opens its task details screen.
5. Work during the sprint
During a sprint, the team works with tasks as usual: changing statuses, adding comments, files, subtasks, and time entries. The sprint remains the planning context and is visible on the task card.
A planned sprint can be edited: goal, dates, and task composition can change before launch. New tasks can be added to an active sprint from the task form through the Sprint field when they really belong to the current cycle.
6. Close or cancel
An active sprint can be closed when the team finishes the cycle or wants to capture the result. Closing detaches current tasks from the sprint, but it does not complete the tasks automatically: unfinished work stays in its current status.
A planned sprint can be canceled before it starts. Its tasks are also detached from the sprint and remain in the project.
Related Guides
Before planning, it helps to groom the Backlog. Project setup and enabling sprints are covered in Projects. The sprint field in the task form is shown in Creating and Editing a Task, and daily task views are covered in Task View Modes.