Sprints

Create, start and complete a sprint, and read its report, burndown and velocity.

Project → Backlog, Board and Burndown

A sprint is a fixed stretch of time in which the team commits to a set of issues. Sprints belong to one project. You plan them in the backlog, work them on the board, and close them with a report showing what got done.

Create a sprint

In a project's Backlog, choose New sprint. You can also use the Sprint button on a board.
Fill in the Sprint name. The other fields are optional: Goal, Start date and End date. On the workspace board, choose the Project too.
Choose Create sprint.

The goal is one sentence about what the sprint is for. It appears in the backlog next to the sprint's dates. You can change the name, goal and dates later with Edit sprint.

Plan and start it

Drag issues from the backlog into the sprint (see The backlog). There is no separate start step: a sprint is running once it has a start date. For a sprint created without one, choose Start in its backlog header. This sets today as the start date.

The board opens on the sprint whose dates include today. If no sprint is running, it opens on the first open sprint. You can run more than one open sprint at a time and switch between them in the board's sprint menu.

Complete a sprint

Choose Complete in the backlog, or Complete sprint... from the sprint's menu on the board.
The dialog shows how many issues are done and lists the ones still open.
Under Move unfinished issues to, choose Backlog, Next sprint (the project's next open sprint by start date), or a specific open sprint.
Choose Complete sprint. The sprint is closed and its report opens.

An issue counts as unfinished when its status is not a final status in its workflow. Next sprint is only offered when another open sprint exists. A new sprint is never created for you, so create the next one first if you want to carry the work over.

A completed sprint can't be completed again or edited, but you can still open its report.

The sprint report

Sprint report shows three totals, each in story points and issues: Committed (everything in the sprint), Completed and Incomplete. A Completion bar gives the share done, by points when the sprint has points and by issue count otherwise. A table lists every issue with its type, status, points and assignee. Open it for any sprint, including completed ones, under Completed sprints in the backlog.

Burndown

A project's Burndown tab charts what is left in a sprint against an ideal straight line from start to end. It opens on the open sprint, and you can pick any other sprint from the menu. Choose what to count:

Story points: the classic burndown.
Issues: for teams that don't estimate.
Estimated hours: from each issue's time estimate.

The header shows Started with, In scope now and Left. If work is added after the sprint starts, the scope goes up, which is why the remaining line can rise.

A burndown needs both a start and an end date on the sprint. An issue counts as burned down on the day it last moved into a done status. If it is reopened and closed again, only the latest close counts.

Velocity

Velocity is the story points and issue count completed in each of a project's recent closed sprints. It appears on the project's Overview and in Insights when one project is selected. The same history drives the capacity line in the backlog and the delivery forecasts on releases and initiatives, which need at least three completed sprints.

Delete a sprint

Delete sprint removes the sprint and sends its issues back to the backlog. The issues themselves are kept. This can't be undone.