Sprints#

What this is for#

A sprint series turns one board into a repeating cycle of boards. Each sprint is a board of its own, named from a prefix and a number — Sprint 1, Sprint 2, and so on — with the same columns, the same groups and the same people as the one before it.

When a sprint ends, Laver creates the next board and moves the unfinished tickets across. Finished tickets stay behind, so the board you have just closed becomes a record of what that cycle actually delivered, and the new board starts as the honest remainder rather than a fresh guess.

If you do not work in cycles, you never need any of this: a board without a sprint series behaves exactly as described in Boards.

Before you start#

• You need to be a workspace owner or admin. Members and viewers can work on sprint boards but cannot create a series or roll one over.
• The board must not already belong to a sprint series.
• Every sprint adds a board to the workspace. The sidebar does not grow by one row per cycle, though — see When a sprint leaves the sidebar.

Start a sprint series#

1. Open the board you want to turn into Sprint 1.
2. Click Set up sprints in the board header.
3. Fill in the dialog:
   • Name prefix — defaults to Sprint. Sprint boards are named "prefix number".
   • Sprint duration — 7, 14 or 21 days, or Custom for anything from 1 to 90 days.
   • Start date and time — optional; leave it blank to start now.
4. Click Create Sprint 1.

Laver creates a new board called Sprint 1, copies the source board's columns, groups and board access onto it, and moves all of the source board's active tickets into it. Not just the unfinished ones — the first sprint takes everything, so the original board is left empty. It is not deleted; you can keep it as a backlog or delete it yourself.

If a board with the name the series wants already exists, creation is refused with "An active board named "Sprint 1" already exists." Rename the other board or pick a different prefix.

What rollover does#

Rollover happens automatically once the sprint's end date passes — Laver checks for due sprints every minute — or on demand from Sprint overview → Start next sprint now → Start next sprint.

Rollover creates the next board and then:

"Unfinished" means precisely one thing: the ticket is not in the column marked as the board's completion column. That mark is set when a board is first created and cannot be moved to a different column afterwards — see Boards — so if you want a different column to count as finished, rename the existing completion column rather than adding one.

The new sprint's dates run from the moment the old one was due to end, so an automatic rollover keeps the cadence even if nobody was looking.

What "locked" means for a finished sprint#

Once a sprint has rolled over, its board is no longer the current sprint, and Laver stops work from flowing into it:

• Creating a ticket on it is refused: "New tasks can only be added to the current sprint."
• Moving a ticket into it from another board is refused: "Tasks can only move to the current sprint board." Closed sprint boards are not offered in the Move to board menu.
• Duplicating a ticket on it is refused: "Tasks can only be duplicated in the current sprint."

It is not frozen, though, and it is worth being clear about that: tickets already on a past sprint board can still be opened, edited, commented on, reassigned, dragged between that board's columns, and deleted. If you need a past sprint to be a true unchanged record, agree with your team that you do not edit it — the product does not enforce it.

What you will see#

On a sprint board, the header carries Sprint n and the cycle's date range under the board name, and the Set up sprints button becomes Sprint overview.

Sprint overview shows:

• The current cycle — its dates and length in days.
• Previous sprints — every earlier board in the series, newest first. Click one to open it; a button then offers to return you to the current sprint.
• Start next sprint now, with a confirmation step that names the sprint the unfinished tickets will move into.

Adding somebody to a sprint#

Board tick-boxes — Admin → People, an invitation, a service account — offer the current sprint of a series and no others, however many cycles the team has run. That one box is the series: tick it and the person is added to the earlier sprints too, so they can read the history from their first day, and their row keeps naming the current sprint as the rollovers go by. Untick it and they come off the series.

See Board access for the rest of how board access works.

When a sprint leaves the sidebar#

A sprint board stops being listed in the sidebar as soon as it is finished — the series has rolled past it, so it is no longer the board work flows into.

The current sprint is always listed, however far past its end date it has run. A series whose rollover is late is exactly when you need to see it.

There is no grace period. A sprint leaves the sidebar the moment the next one starts, including the one you closed today; read it back from Sprint overview → Previous sprints.

Nothing is deleted and nothing becomes unreachable. A sprint that has left the sidebar is still listed under Sprint overview → Previous sprints, still opens from a link or a bookmark, and reappears in the sidebar for as long as you are looking at it — so you can always see where you are.

Stopping a series#

There is no "end series" button. Archiving the board that is the current sprint switches the series off, and no further rollovers happen. Earlier sprint boards stay where they are and remain readable.

Restoring that board later brings it and its tickets back, but it does not switch the series on again — rollovers stay stopped until you start a new series. See Boards for how to restore an archived board.

Sprints and API keys#

Sprint endpoints accept your signed-in session only. An API key can read and write tickets on a sprint board but cannot create a series or trigger a rollover.