Sprint
Sprint templates
A sprint template contains stages and is used to define a specific order for these stages. When a sprint is created, a sprint template must be assigned to it. Then, when an issue is added to a sprint, the issue will be in the first stage set up in the sprint template. Issues added to the sprint will have to go through all the stages set up in the template, until they reach the last stage, meaning the issues are completed inside the sprint.
Example
To create its sprints, a company chooses to set up 2 sprint templates:
- the first template will be used by the development team and contains the following stages: 1 - to do / 2 - DEV ongoing / 3 - done;
- the second template will be used by the quality control team and contains the following stages: 1 - to do / 2 - QUAL ongoing / 3 - done.
Sprint templates are set up from the Tools screen, in Help Desk setup > Sprint > Sprint templates. The Result screen displays the list of all existing templates.
To create a sprint template:
| 1 | In the results screen, click on  in the action bar. |
The Sprint template screen opens.
| 2 | Fill in the following fields: |
| Field | Description |
|---|---|
| Code |
Enter a code to identify the template. This code must be unique. |
| Valid until |
If needed, enter a validity end date. After this validity date has passed, the template can no longer be used. |
| Label | Give a name to the template. |
| Stage |
Select a stage from the help list. Repeat the process to add all the desired stages. Stages are listed one after the other in the table. To change the order, select a stage in the table and use the |
and 
arrows. To remove a stage from the table, select it then click on 
.| 3 | Save the template. |
The template is created and can be used to create new sprints. Update the results screen to display the new template in the list.
To edit a template, open the desired template then click on 
in the action bar.
To delete a template, open the desired template, click on 
in the action bar then confirm the deletion.
Issue stages inside a sprint
An issue can go through multiple stages inside a sprint. The different issue stages can be set up to meet the specific needs for managing software development.
Example
To manage its issues, a company chooses to set up 4 issue stages:
- to do for issues that have just been added to a sprint;
- DEV ongoing for issues that are being processed by the development team;
- QUAL ongoing for issues that are being processed by the quality control team;
- done for issues that have been processed.
Stages are set up from the Tools screen, in Help Desk setup > Sprint > Issue stages - sprint. The Result screen displays the list of all existing stages.
To create a stage:
| 1 | In the results screen, click on in the action bar. |
The Issue stage - sprint screen opens.
| 2 | Fill in the following fields: |
| Field | Description |
|---|---|
| Code |
Enter a code to identify the stage. This code must be unique. |
| Valid until |
If needed, enter a validity end date. After this validity date has passed, the stage can no longer be used. |
| Label | Give a name to the stage. |
| 3 | Save the stage. |
The stage is created and can be used in a sprint template. Update the results screen to display the new stage in the list.
To edit a stage, open the desired stage then click on in the action bar.
To delete a stage, open the desired stage, click on in the action bar then confirm the deletion.
