Backlog planning & sprints

What can I do on the backlog planning page?

Scrum projects have a Board tab and a Backlog tab. The Backlog tab shows the running and planned sprints as sections — with dates, issue count and points — followed by the backlog.

• Drag issues between sprints and the backlog, or reorder within a section
• Select several (checkbox or shift-click) and move them together
• Use Create issue at the end of a section to add straight into it
• Create, edit, start and complete sprints from here
• Move a row with ⇧↑ / ⇧↓ or its ⋯ menu; on phones, long-press and drag

How do I create and start a sprint?

A new sprint's dates default to the day after the latest sprint ends, with the same length. You can always change them, and date ranges may overlap.

Every Start opens the Start sprint form: edit the name, duration (1–4 weeks or custom), start, end and goal, and check the issue count, points and warnings (no issues, no points, overlap with a running sprint). A planned start in the past becomes today, keeping the length. Confirm and you land on that sprint's board.

When no sprint is running, the board shows the next planned sprint locked — cards open, but nothing moves — with Start sprint for project admins.

Can several sprints run at once?

Yes, when a project admin turns on Parallel sprints in Project settings. It is off by default: a sprint can start only while no other sprint is running, and the Start sprint form explains why when it cannot.

• The board gets a sprint selector: all running sprints (the default) or one at a time
• On all sprints, cards show a sprint chip, and dropping from the backlog asks which sprint
• The burndown and points follow the selected sprint
• An issue is in one sprint at a time, and sprints are closed one by one
• Turning the switch off while several run lets them finish, but no new one starts until one is left

Where does unfinished work go when a sprint closes?

When closing, choose where unfinished issues go: the backlog, a new sprint (dated right after the latest one) or a planned sprint — never into a sprint that is already running.

Who can manage sprints?

• Project admin: create, rename or re-date, set the goal, start and close sprints, and switch parallel sprints
• Member: move issues into or out of sprints and reorder them
• Viewer: read only

How are sprints stored, and how is the burndown calculated?

A sprint is one .md file in the project's sprints/ folder, with state planned, active or closed. The burndown uses the story points of the sprint's issues, recorded daily — one sprint at a time, in the app or over MCP (get_burndown).

---
id: S-12
name: Sprint 12
state: active             # planned | active | closed
start: 2026-09-15
end: 2026-09-29
goal: Ship login and session for QA
---