Backlog and sprints

Planning sprints on a scrum board's backlog.

The backlog page of a scrum board lists the open sprints with their tickets, and below them the backlog: every open ticket that is in no sprint, in rank order.

Note

An administrator can switch sprints and the backlog off for a workspace (Modules and features). If you do not see them in yours, they are switched off there: ask an administrator if you need them.

Planning

Drag tickets from the backlog into a sprint, between sprints, or back to the backlog. Drop a ticket above or below another to set its order; the order is the same rank the board uses. As you drag, the row leaves its list and travels with the pointer, and the row you are about to land above opens a space its size, drawn as a dashed box, so you can see the resulting order before you drop. Every row also carries a Move to… menu listing the open sprints and the backlog, so a ticket can be planned from the keyboard or on a touch screen; it goes to the end of the list you choose.

Moving a ticket out of a sprint keeps a record that it was there, so reports on carried-over work stay accurate.

Sprint lifecycle

Project administrators see the sprint controls:

  • New sprint creates a future sprint with a name, an optional goal and optional dates.
  • Start sprint makes a future sprint active. A board runs one sprint at a time, and starting asks for an end date; the start defaults to now and the end to two weeks later.
  • Complete sprint closes the active sprint. Finished tickets stay in it; the rest go to a sprint you choose or back to the backlog.
  • Edit changes the name, goal and dates. Delete removes a future sprint and returns its tickets to the backlog.

Sprints imported from Jira keep their names, goals, dates and history.