ACME-142points
ACME-151points
ACME-92points
Sprints and boards
Plan a sprint. See exactly what moved.
Order the backlog, plan a sprint with a goal and story points, and follow it on a board. When it ends, you decide where the unfinished work goes, and the burndown keeps an honest record.
Rather try it here? Move cards on a demo board
Make invitations clearer
4 Oct – 17 Oct 20264 days left21 of 34 points resolved
Cards by status:
- Open 3
- In Progress 2
- Fixed 6
Open3
5 points
ACME-142points
Invite email subject names the org
ACME-151points
Resend invite from the members list
ACME-92points
Upload stalls at 100% on slow links
In Progress2
8 pointsmax 2
ACME-115points
Swimlane header overlaps count
ACME-103points
Invite landing shows the inviter
Fixedresolved6
21 points
ACME-123points
Invite link blank after it expires
ACME-68points
Project-scoped invite links
ACME-55points
Accept invite while signed in
ACME-43points
Invite expiry setting per org
ACME-131points
Invite expiry date shown in UTC
ACME-21points
Password hint is cut off on small screens
Planned · Sprint 09
19 Oct – 30 Oct 2026
4 issues, 11 points. Waiting for its start.
Active · Sprint 08
4 Oct – 17 Oct 2026
4 days left. One active sprint per project.
Completed · Sprint 07
21 Sep – 2 Oct 2026
27 of 30 points resolved. ACME-10 moved on to Sprint 08.
From an ordered backlog to a running sprint.
The backlog is every issue in no sprint. You decide what moves into the next one; nothing is planned for you.
- Order the backlog. Drag a row by its grip, or focus the grip and use Space, the arrow keys and Space again. The board shows cards in the same order.
- Move work into a planned sprint. Drop rows into it, or bring over every unresolved issue of the running sprint when you create the next one.
- Set a goal and points. The goal is Markdown. Story points are whole numbers from 0 to 999; an issue without them reads Not estimated.
- Start it. It starts on the day you start it and keeps its planned end date, which drives the days-left countdown. One sprint runs at a time in each project.
Sprint 08Active
Sprint 09Planned
Goal: Members can manage invitations without asking an admin.
- ACME-16Reminder email before an invite expiresFeature3 points
- ACME-17Show who invited each memberFeature2 points
- ACME-18Revoke a pending invitationFeature5 points
- ACME-19Invite form explains each roleTask1 point
Backlog
- ACME-20Members list stops at 50 peopleBug3 points
- ACME-21Avatar initials clash for similar namesBug2 points
- ACME-22Remember the last board filterFeatureNot estimated
- ACME-23Due date picker starts on MondayTask1 point
3 more issues
One sprint, read the way the team works.
A board shows one sprint, or every open issue in the project, as columns of cards. A Project Admin chooses what the columns and rows mean, per board.
Columns by status, priority or type.
A column can hold several values, such as Open and Reopened. Moving a card gives the issue that column’s first value.
Swimlanes for people or epics.
One row per assignee, priority or type, or one row per epic with its issues inside. Cards without an epic sit in Uncategorized, always last.
WIP limits warn, they never block.
Set a minimum and a maximum per column. Over the maximum the limit turns red, under the minimum amber, and the card still moves.
Counts follow the filter.
Type a query above the board and each column reads 3 of 8. WIP limits still count all eight.
Open3
In Progress2
Fixed6
ACME-115points
ACME-103points
ACME-123points
ACME-68points
ACME-55points
ACME-43points
ACME-131points
ACME-21points
Major4
Normal6
Minor1
ACME-123points
ACME-92points
ACME-68points
ACME-55points
ACME-142points
ACME-151points
ACME-115points
ACME-103points
ACME-43points
ACME-21points
ACME-131points
Bug6
Feature3
Task2
ACME-123points
ACME-92points
ACME-115points
ACME-55points
ACME-131points
ACME-21points
ACME-151points
ACME-103points
ACME-68points
ACME-142points
ACME-43points
Open3
In Progress2
Fixed6
Alex Lee5
ACME-151points
ACME-103points
ACME-123points
ACME-55points
ACME-131points
Casey Kim2
ACME-142points
ACME-115points
Jordan2
ACME-68points
ACME-21points
Sam Ortiz1
ACME-43points
Unassigned1
ACME-92points
The same eleven cards of Sprint 08, keys and points only. Every project starts with one board: To do, In progress and Done, with a row per epic. Here the epic ACME-3, Make invitations clearer, would hold four of the cards.
A sprint ends with a decision, not a pile of forgotten work.
Move two cards on Sprint 08 and watch the counts. Then finish the sprint: you choose where the unfinished issues go, the backlog or a planned sprint. Nothing is chosen for you.
Move a card
Both cards moved, then Sprint 08 finished with its unfinished issues sent to Sprint 09. With JavaScript on, you can make these moves yourself.
Make invitations clearer24 of 34 points resolved
Open0
0 points
ACME-142points
Invite email subject names the org
ACME-151points
Resend invite from the members list
ACME-92points
Upload stalls at 100% on slow links
Moved to Sprint 09
In Progress0
0 pointsmax 2
ACME-142points
Invite email subject names the org
ACME-115points
Swimlane header overlaps count
ACME-103points
Invite landing shows the inviter
Moved to Sprint 09
Fixedresolved7
24 points
ACME-123points
Invite link blank after it expires
ACME-103points
Invite landing shows the inviter
ACME-68points
Project-scoped invite links
ACME-55points
Accept invite while signed in
ACME-43points
Invite expiry setting per org
ACME-131points
Invite expiry date shown in UTC
ACME-21points
Password hint is cut off on small screens
Moved to Sprint 09
| Column | Before | Now |
|---|---|---|
| Open | 3 · 5 pts | 0 · 0 pts |
| In Progress | 2 · 8 pts | 0 · 0 pts |
| Fixed | 6 · 21 pts | 7 · 24 pts |
| Unfinished | 5 · 13 pts | Moved out |
Finish Sprint 08
4 issues, 10 points unfinished. Where do they go?
Move unfinished issues to
Pick a destination first.
- Backlog · Issues in no sprint
- 7 issues, 8 points
- Sprint 09 · Planned, 19 Oct – 30 Oct 2026
- 4 → 8 issues, 11 → 21 points
- Sprint 08
- Completed. Keeps 7 issues, 24 points it resolved.
- History of each moved issue
Sprint: Sprint 08 → Sprint 09
A burndown that shows when the scope moved.
The figures are recorded every night and when the sprint starts and finishes, so the chart shows how the sprint really went even after issues are edited. Scope added after the start is its own line, so we finished nothing and they added 6 points on Tuesday look different. Measure it in story points, issue count or remaining estimate.
Burndown · Sprint 07 · Story points
- Remaining
- Ideal
- Scope added after the start
0102030+6 added 29 Sep
| Date | Remaining | Ideal | Added | Done |
|---|---|---|---|---|
| 21 Sep | 24 | 24 | 0 | 0 |
| 22 Sep | 24 | 21.3 | 0 | 0 |
| 23 Sep | 21 | 18.7 | 0 | 3 |
| 24 Sep | 18 | 16 | 0 | 6 |
| 25 Sep | 16 | 13.3 | 0 | 8 |
| 26 Sep | 16 | 13.3 | 0 | 8 |
| 27 Sep | 16 | 13.3 | 0 | 8 |
| 28 Sep | 13 | 10.7 | 0 | 11 |
| 29 Sep | 19 | 8 | 6 | 11 |
| 30 Sep | 14 | 5.3 | 6 | 16 |
| 1 Oct | 8 | 2.7 | 6 | 22 |
| 2 Oct | 3 | 0 | 6 | 27 |
Added is scope added since the start. Done is points resolved.
Made for sprint and board work, one project at a time.
Teams that plan in sprints and follow them on a board get a backlog, sprints, boards and a burndown that agree with each other, one project at a time. It is not an enterprise portfolio planner.
A good fit for
- A team that plans one sprint at a time in each project, with a goal and story points.
- People who want the backlog, the board and the burndown to tell the same story about a sprint.
- Teams whose AI agent should plan and move work with the same permissions as they have.
Not built for
- Portfolio planning across projects. A sprint belongs to one project, and so does a board.
- Automatic sprint planning or velocity forecasts. You choose the work; the burndown records what happened.
- Status changes from deployments. Cards move when someone moves them, or when an automation acts on a branch, a pull request or a merge.
Questions about sprints and boards.
What happens at the end of a sprint, what WIP limits do and who can change what. Details are in the manual.
Do unfinished issues roll into the next sprint on their own?
No. Finishing a sprint asks where its unfinished issues go: the backlog or a planned sprint you pick. Nothing is chosen for you. Resolved issues stay with the finished sprint, and each moved issue’s history records the change of sprint. Sprints in the manual
Can we use a board without sprints?
Yes. Pick All open issues in the sprint picker and the board shows every unresolved issue in the project, in a sprint or not. A project with no sprint running or planned opens its board that way, so a team that never plans a sprint still has a board.
Do WIP limits stop people moving cards?
No. A column can have a minimum and a maximum number of cards. Over the maximum its limit shows in red, under the minimum in amber, and the move still goes through. Limits count every card in the column, whatever the filter.
Who can plan, start and finish sprints?
Project Admins and organisation admins plan, start, finish and delete sprints. Anyone who can edit issues, Contributors and up, moves issues into and out of sprints and reorders them. Observers see the backlog but cannot drag.
Does it plan sprints or forecast velocity for us?
No. You choose what goes into a sprint and set the points yourself, as whole numbers from 0 to 999. The burndown records what happened each day, including scope added after the start; it does not predict what comes next. Reports
Can an AI agent work with sprints and boards?
Yes. Everything on the backlog and the board is also available through the MCP tools, with the same permissions as in the app, so an agent can move issues into a sprint or read a burndown for you. MCP and AI agents
Plan your next sprint here.
Join the beta, create a project, order the backlog and start a sprint. Invite the team when the board looks right.