DocsModulesSprints: plan a sprint, schedule tasks and track progress

Sprints: plan a sprint, schedule tasks and track progress

The Sprints module brings agile planning with target/actual tracking to your board. Create a sprint, pull tasks in from the backlog, and follow progress and burndown at a glance.

Prerequisites
  • You're signed in and your organization has the "Sprints" module activated.
  • Optional: a project to attach the sprint to, and backlog tasks you want to schedule.
  1. 1

    Filter sprints and keep an overview

    The All, Active, Planning and Completed tabs each show a count in brackets and filter the list. Every row shows a status badge, the linked project (if any), its date range, task count with estimated hours, and — once a capacity is set — a usage bar with target/actual hours.

  2. 2

    Start and complete a sprint

    A sprint in "Planning" status reveals a green Play icon on hover to start it. An active sprint shows a checkmark icon to complete it instead. The same actions are also available as buttons at the top once you open the sprint itself.

  3. 3

    Choose Board or Dashboard

    Inside a sprint, switch between Board (a table of every sprint task with status, target and actual hours) and Dashboard (a status-distribution pie chart, a burndown chart, and tasks per week). Completed or cancelled sprints automatically show a retro view on the Board tab instead, with Done and Not done columns.

  4. 4

    Open Sprints

    Open "Sprints" from the main menu (route /sprints). The list shows every sprint in the organization, filtered to "All" by default.

    Sprint overview with filter tabs and two sprint rows
  5. 5

    Create a new sprint

    Click "Create Sprint" in the top right. Only the name is required — sprint goal, start/end date and capacity (target hours) are optional, but they determine whether a usage bar and a burndown with a timeline show up later. "Create Sprint" saves it; the new sprint then appears in "Planning" status at the top of the list.

    "New Sprint" form with a filled-in name and goal
  6. 6

    Add tasks from the backlog

    Open a sprint via "Board" and click "Add task from backlog" (or "Add tasks" if the sprint is still empty). The search field filters every task not yet assigned to a sprint; clicking "Add" pulls the task into the board immediately without closing the list.

    "Add task to sprint" modal listing available backlog tasks
  7. 7

    Maintain target hours per task

    In the board, click a row's target value (or "— h" if none is set yet), enter the estimated hours and confirm with Enter. This updates the task's own estimated hours — not just within the sprint. The "Total" row at the bottom of the table and the stat tiles above (period, tasks, effort, capacity, and project budget if applicable) update automatically.

    Sprint board with three tasks, target hours and a total row
  8. 8

    Track progress on the Dashboard

    Switch to the "Dashboard" tab within the sprint. The status distribution shows Open/In progress/Done as a pie chart, the burndown compares target and actual lines across the sprint period, and "Tasks per week" below lists the breakdown by calendar week.

    Sprint dashboard with status distribution and burndown chart
Common pitfalls
  • New sprints start in "Planning" status

    A freshly created sprint isn't automatically active. Only the Play button in the list, or "Start Sprint" inside the sprint, sets it to "Active" — before that it only shows up under the "Planning" filter.

  • No capacity, no usage bar

    The target/actual bar in the list and the capacity tile inside the sprint only appear once a capacity in hours has been entered, at creation or later. Without that value, the capacity display is missing entirely.

  • Completed sprints only show the retro, not the board

    Once a sprint is "Completed" or "Cancelled", the Board tab shows only the retro breakdown of Done/Not done. Tasks can no longer be added or removed there.

Related articles

More articles are coming soon.

Last reviewed on 2026-09-11Couldn't find your answer, or still stuck? Go to support