The backlog

Rank the work nobody has planned yet and drag it into sprints.

Project → Backlog

The backlog is where a project's unplanned work waits, in the order the team wants to do it. It is also where you plan sprints: drag issues from the backlog into a sprint, or between sprints.

Open the backlog

Open a project and choose the Backlog tab. The page has two parts:

  • Backlog on the left: every issue in the project that is not in a sprint.
  • Each open sprint on the right, with its issues, its dates, its goal and its total story points. Completed sprints are listed under Completed sprints at the bottom.

Sub-issues and issues waiting in Triage are not listed. Sub-issues are planned with their parent.

Rank issues

  1. Drag an issue up or down by its row. A line shows where it will land.
  2. Or, from the keyboard, focus a row and press Alt + Up or Alt + Down.

The order is saved straight away and is the same for everyone. Ranking works inside the backlog and inside each sprint.

Move issues into a sprint

  • Drag an issue from the backlog onto a sprint, at the position you want.
  • Or use the Move to sprint menu on the issue's row.
  • To move an issue between sprints or back, use the menu on its row in the sprint and choose another sprint or Backlog. You can also drag it onto the backlog list.

Estimate issues

Estimates are set on the issue itself, not on the backlog row. Open an issue and fill in Story points (0 to 100), or a time estimate in Track time (for example 2h 30m). Each sprint header adds up the story points of its issues.

Under each sprint's dates, a capacity line compares what the sprint holds with what the team usually finishes:

  • Once the project has three completed sprints, it shows what is committed against the typical amount from recent sprints, and says whether that is in line with them, more than any of them finished, or less. It counts in story points when the team estimates, and in issues otherwise.
  • Until then it says Velocity appears here after three completed sprints.
  • When issues have time estimates and team members have a weekly capacity set in Workload, it also compares the estimated hours with the team's capacity hours over the sprint's dates.

Manage sprints from the backlog

Choose New sprint to create one. Each sprint header has Start (only for a sprint without a start date), Complete, Open board, and a menu with Edit sprint, Sprint report and Delete sprint. See Sprints for what each one does.