 This page only applies to Scrum boards. If you are using a Kanban board, please see Releasing a Version (Kanban).
On the final day of the sprint the team will complete the sprint — this will usually occur immediately prior to the sprint demo and retrospective. Any issues not completed at the end of the sprint will be returned to the backlog (or to the next planned sprint, if you have one) as they did not meet the team's definition of "Done". To end the active sprint, - Login to JIRA.
| Include Page |
|---|
| _RapidBoardNav_instructions |
|---|
| _RapidBoardNav_instructions |
|---|
|
- Click Work.
- Click the cog dropdown, next to the sprint name, to display a dialog box (see Screenshot 1 below).
Or, if you are using GreenHopper 6.0.1 or earlier, click the arrow icon at the top of the Done (rightmost) column. - If you wish, edit the Sprint Name, Start Date or End Date.
- Click the Complete Sprint button.
You will need to have the JIRA 'Project Administrator' in the project(s) whose issues are included in the sprint.
When you try to close a sprint, and you have parent issues not Done but all sub-tasks are Done, or visa-versa, you will be prompted to make the parent Done before continuing. For issues to be interpreted as 'Done' on your Scrum board their status needs to be mapped to that column, so if you're receiving errors for parents or sub-tasks that you believe are in fact Done, ensure that they are mapped correctly. - You will be taken to the Sprint Report. Your issues will move out of Work mode. Any incomplete issues will move back into the backlog and will be visible in Plan mode.
| 