Plan, start and complete a sprint
A sprint groups a deliberate set of project issues around a goal. Prepare its membership in Backlog, set its dates when starting, and use the completion dialog to preserve finished work while choosing the destination for everything still unfinished.
Backlog → Create sprint → Start sprint / Complete sprintWhat you’ll learn
- Prepare scope before starting.
- Set a goal and consistent dates.
- Keep completed history and move unfinished work.
Captured in Boilerrum with an illustrative project. The app interface is shown in English.
In this guide
01
Create the planned sprint
Open Backlog and select Create sprint. A new planned sprint appears in Sprints with a generated name and issue count. Inspect the new section before adding work, especially if other planned or completed sprints already exist. An empty planned sprint cannot be started, so treat this as a planning container until you have selected its issues.
02
Move ready issues into the sprint
Drag ready rows from Backlog into the sprint, or change Sprint in an issue’s Details. You can also create a titled issue directly inside an open sprint. Review each item’s expected result, assignee and estimate before committing it. Check the section’s issue count and open a sample issue to verify that its Sprint field names this sprint.
03
Start with an explicit goal and dates
Select Start sprint. In the dialog, review Sprint name and enter Sprint goal, Start date and End date. The name is required, and an end date earlier than the start is rejected. Only one sprint can be active at a time. Choose Start sprint and confirm the section now shows active, together with the goal you entered.
04
Track progress through issue statuses
During the sprint, update issues through their Status control or board column moves. Keep the goal visible in Backlog and use Details for comments, ownership changes or work logs. A sprint is not complete merely because its end date has passed. Before closing it, verify which issues are in a done-category or terminal workflow status.
05
Choose a destination for unfinished work
Select Complete sprint on the active sprint. Read the completed and unfinished counts before confirming. If unfinished issues remain, use Move unfinished issues to and choose Backlog or another non-completed sprint. Completed issues stay in this sprint’s history. Choose Complete sprint only after the destination matches the next planning decision for the remaining work.
06
Verify history and the next queue
Inspect the completed sprint section or completed history and verify its retained issues. Check the chosen destination for each unfinished item, then open one item to confirm its Sprint field changed consistently. Completed sprint membership is protected from ordinary moves. Reload in the same browser to verify local persistence before starting another planned sprint or relying on the recorded history.
A completed sprint with its finished work preserved and every unfinished issue placed in a deliberate next destination.