Backlog and sprint planning on one screen.
Every unplanned issue in one list, with a clear count of how many still need an estimate. Your sprints are listed right beside it, so planning is as simple as dragging an issue across.
Backlog items, story points, critical issues, and the number nobody has sized yet. Three of those are what you know. The fourth is what you do not, printed the same size.
The backlog
The backlog, with sprints beside it.
Every issue shows its type, key, priority and estimate, and anything without an estimate shows an empty ring so it stands out. Filter to tasks, bugs or stories, order the list yourself, and drag issues into a sprint from the panel on the right.
Drag issues into sprints to plan your next iteration
Unestimated items get their own count.
See how much work still needs an estimate.
The top of the screen shows backlog items, story points, critical issues and, just as prominently, how many issues have no estimate yet.
- See backlog items, story points, critical issues and unestimated counts at a glance
- Spot issues with no estimate by their empty ring
- Filter to tasks, bugs or stories, each with its own count
- Search the backlog by title or key
- Order the list yourself, and it stays how you left it
Drag an issue into a sprint.
Every sprint is listed with its dates, its state and how many issues it holds.
- Drag an issue from the backlog straight into a sprint
- See which sprint is active and which have closed
- See how many issues each sprint already holds
- Plan against capacity that already knows who is on leave
- Create a new issue right here, without switching to the board
Access
Who can do what.
Anyone can add to the backlog and estimate their own work. Ordering the list, and choosing what goes into the next sprint, belongs to whoever runs delivery.
See the backlog and what is planned for each sprint.
Raise an issue and estimate your own work.
Order the backlog and pull work into a sprint.
Manage issue types and decide who can plan sprints.
Admin is the highest role and is not limited by these permissions, so keep it to the few people who genuinely need it.
One iteration, start to finish
Follow one issue from raised to planned.
A new issue arrived without an estimate, so it showed up in the unestimated count instead of hiding in the total. Once the team sized it, they dragged it into Sprint 12 on the same screen, with capacity that already knew two people were on leave.
A new issue joins the backlog, and the unestimated counter goes up by one.