Sprints

Last updated About 1 hour ago

Sprints ​

A sprint is a named window of time in which work gets done – two weeks of work, a release cycle, a maintenance round. Sprints are their own area in the navigation and lie across projects: what sits in a sprint can come from any number of lists.

A series, not one at a time ​

You do not create individual sprints. You create a sprint series, and it produces them continuously:

FieldMeaning
Namee.g. "Backend team" – shown wherever the sprint appears
Start dateThe anchor everything is counted from
Duration (days)How long a sprint runs
Cooldown (days)The break between two sprints – 0 for back-to-back
MembersWho plans and sees (teams and individual people)
Progress measured inNumber of items, hours, or story points
ColourTo tell several series apart

That gives the cadence: "10 days of work, 4 days cooldown — a new sprint every 14 days." Sprints are numbered (Sprint 14); a name of your own sits next to the number, it does not replace it.

A series is not a team

It has its own member list – any mix of teams and people, like a list. A release train, a squad, and a maintenance rhythm may all touch the same work and still be separate series.

If you change the cadence, the new one applies from the next sprint onwards. Past sprints keep their dates – otherwise your own history would shift retroactively.

Working in a sprint ​

The view shows the running sprint. The pills take you to previous, next, and the one after next; "Back to the running sprint" returns you.

  • Group by status or sort by last activity
  • Filter by person – "Me" or "Everyone"
  • Add a task right in the sprint; the composer creates it in a project and can start it as an AI job straight away
  • Drag a task to move it into another sprint

During a cooldown it says "No sprint is running right now". That is not an error, it is the break between two sprints.

Putting a task into a sprint ​

On the item itself, via the Sprint property: current sprint, next sprint, the one after next, or remove from sprint.

Two rules worth knowing:

  • At most one sprint per series. Moving a task into another sprint of the same series replaces the previous assignment.
  • Several series at once are fine. The same task may sit in the backend team's sprint 14 and the release train's sprint 3.

Sub-tasks do not inherit the sprint. They do not follow their parent automatically – deliberately, so a part of the work can also be done later.

With story points (the estimate property on the item) the series measures progress, if it is set to do so.

Completing a sprint ​

On completion you decide what happens to unfinished work:

  • Carry over – it moves into the series' next sprint.
  • Do not carry over – it leaves the sprint and sits in its list's backlog again.

Finished tasks stay where they are. The sprint records how it was closed – the question "where was this before?" is answered by the sprint, not by the task.

Visibility ​

Membership of a series decides who may plan and see the sprint. It grants no access to tasks: what you see in a sprint is still bounded by your access to the respective list.

That is why a note like "3 items from projects you cannot access" appears below the list sometimes. Those tasks exist and count towards progress – you just do not see them.

With the AI ​

The AI can read sprints and assign tasks – "What is still open in the current sprint?" or "Put this into the next sprint". The tools are documented under MCP tools: sprints.

Not to be confused with "Cycle (old)"

The list type Cycle (old) is an older feature inside a single list. Sprints are independent of it and sit across projects.