Skip to content

Stints

A stint is a time-boxed iteration for a team — a fixed window of time (a week or two, typically) that a set of tasks is scheduled into.

You can create a stint manually from a team’s Stints settings with New stint: give it a name, a start date, and an end date.

Or a team can turn on Cadence, which auto-generates upcoming stints on a schedule and rolls unfinished work forward into the next one automatically.

Stint names can also be generated for you — see Stint name templates below.

Opening a stint shows a two-pane layout: the stint’s tasks, grouped by status, on one side, and an insights panel on the other — the date range, description, a breakdown by member, label, and project, and a burndown chart of progress. From there you can edit the stint, copy a link to it, or export it to CSV.

You can assign a task to a stint directly from the task, using its stint field.

A team can also turn on task automation, so tasks are added to the current stint automatically:

  • When a task moves into progress or review.
  • When a task is marked done.
  • When an active task’s due date falls within the stint’s dates.

All three are off by default — turn on whichever fit how your team works.

Instead of naming every stint by hand, a team can define a naming template — for example Stint ${n} — with tokens for things like the sequence number, year, quarter, month, week, or date. You can also pick a codename theme (Docker-style, pop-culture, classic, or NATO alphabet) to give each stint a memorable name alongside its number. A preview shows you what the next few stint names will look like before you save.