Sprints
Before you start#
You need to be a workspace owner or admin, and the board must not already belong to a series.
Start a sprint series#
Set up sprints in the board header: name prefix (default Sprint),
duration (7, 14, 21 or custom days), optional start date. Laver creates
Sprint 1, copies the source board's columns, groups and access onto it, and
moves all of the source board's active tickets across — the source board
is left empty, not deleted.
What rollover does#
Automatic once the end date passes (checked every minute), or on demand from Sprint overview → Start next sprint now.
| What | Happens to it |
|---|---|
| Tickets not in the completion column | Moved to the new board, keeping their column and group |
| Tickets in the completion column | Left behind on the sprint that just ended |
| Columns, groups, board access | Copied to the new board |
| Comments, attachments, assignees, labels, success criteria | Travel with the ticket that moves |
"Unfinished" means precisely: not in the completion column. That mark is set when a board is created and cannot move to a different column afterward.
Finished sprints are locked, not frozen#
Creating, moving-in or duplicating a ticket on a past sprint board is refused — but tickets already there can still be opened, edited, commented on and deleted. The product does not enforce a true unchanged record; agree with your team if you need one.
Sprint overview#
Current cycle dates, Previous sprints (newest first), and Start next sprint now.
Stopping a series#
There is no "end series" button — archiving the current sprint board switches the series off. Restoring it later does not switch rollovers back on.
Sprints and API keys#
Sprint endpoints accept a 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 — see API keys.