Managing sprints
Sprints are used to manage the workload in order to process help desk issues. A sprint represents a period of time and is associated with issues. The number of issues depends on the number of employees available and the difficulty assessed for each issue.
Stages can be used to track how issues are progressing inside a sprint as accurately as needed.

Two types of data must be set up to use sprints:
- issue stages inside a sprint;
- sprint templates.
Reference
For more information about the sprints setup, see Sprint.

Existing sprints can be accessed using the sprint search screen. This screen enables users to set search criteria in order to get the list of all the sprints matching these criteria.
To open the Sprint search screen, go to Help Desk > Sprint search from the top menu.
This search screen works just like all the other search screens available in Akuiteo.
Reference
For more information about searches in Akuiteo, refer to the Search and display.

Sprints can be created:

1 | From the top menu, go to Help Desk > Sprint search to open the search screen, then click on |
The Sprint screen opens.
2 | In the Sprint screen, fill in the following fields: |
Field | Description |
---|---|
Code | Enter a code to identify the sprint. This code must be unique. |
Sprint template |
Select a sprint template from the help list. A sprint template defines the different stages each issue will have to go through inside the sprint. The template also defines the order of these stages. This way, the template enables users to define the order once and to quickly create new sprints. The help list displays all srpint templates setup on the company used for connection and the ***** company. |
Label | Give a name to the sprint. |
Period | Enter the start and end dates for the sprint. This period is for informational purposes only. |
Status |
This field is always grayed out and cannot be modified. It shows the sprint status depending on the actions taken. The sprint status can be:
|
Max. capacity |
Define the sprint's maximum capacity. This field is optional and enables users to associate a maximum workload with a sprint. The value specified (integer number) is defined arbitrarily by users to suit their specific needs. Example A manager cint for the development team. He sets the sprint's maximum capacity to 20. He adds issues to the sprint and determines the workload for each issue: 1 for issues that will be quickly resolved, 2 for issues that are easy to resolve but will take more time, and 3 for complex issues. When the total capacity reaches 20, the sprint's maximum capacity is reached and the manager does not aissues to it. |
Total capacity |
This field is only displayed and filled in if the Max. capacity field is specified. This field is automatically filled in by adding up all the workload assessment made for each issue. |
Description | Describe the sprint. This description is optional. |
3 | When the fields are filled in, save the sprint. |
The sprint is created and can be associated with issues.

A new sprint can be created quickly by duplicating an existing sprint.
To duplicate a sprint, click on in the sprint's action bar. The details of the original sprint are filled in automatically. The Code must be filled in and be different from the original sprint's code since it must be unique. The issues linked to the original sprint are not included in the new sprint.

Issues can be linked from a sprint. When an issue is linked to a sprint:
- The issue's progress is managed in the sprint's context using issue stages;
- The issue's capacity is determined in the sprint's context;
- The issue's priority, which is different for each issue, is displayed in the sprint's context to sort the issues by priority;
- The person assigned to the last non-completed task is displayed for each issue.
The issues linked to a sprint are managed in the sprint's Linked issues tab.
The number of linked issues is also displayed in the main tab: an X linked issue(s) link is displayed to access the Linked issues tab.

Important
An issue cannot be linked to a completed sprint.
1 | In the Linked issues tab, click on |
The Link issue window opens.
2 | In the Link issue window, fill in the following fields: |
Field | Description |
---|---|
Sprint | Displays the sprint's code. The issue will be linked to this sprint. |
Issue | Select an issue from the help list. This issue will be linked to the sprint. |
Issue stage |
Select the stage from the help list. The issue stage shows the issue's progress inside the sprint. This value is not related to the issue's status and state. |
Issue complexity |
Enter a value to assess the workload of the issue inside the sprint. This workload is determined by users depending on the team's needs: the workload's unit can be in days, in hours, in difficulty levels, and so on. The value entered is added to the Total capacity field available in the sprint's main tab. The Total capacity field is filled in automatically by adding all the complexity values of all the linked issues. This capacity is also displayed as a percentage on the right: "X% of the issue's Max. capacity is used". |
3 | When the fields are filled in, click Validate. |
The sprint is linked to the selected issue. The links are displayed in a table in the Linked issues tab of the sprint, as well as in the Linked sprints tab of the issue.

When you need to link multiple issues to a sprint, adding them one by one can take some time. For example, if multiple issues have not been completed inside a sprint, these issues need to be quickly transferred to another sprint.
1 | Open the Linked issues tab in the new sprint. The sprint must not be in modification. |
2 | In the issue search screen, fill in the relevant criteria to find the issues to be transferred, then start the search. |
3 | From the search results, select the desired issues, drag them to the new sprint and drop them in the table. |
Important
The sprint and the search results must both be displayed.
The selected issues are linked to the sprint. The links are displayed in a table in the Linked issues tab of the sprint, as well as in the Linked sprints tab of the issues.

To edit an issue linked to a sprint: in the Linked issues tab of the sprint, click on for the desired issue.
The issue stage inside the sprint can be updated directly from the table in the Linked issues tab. Use the and
arrows to update the stage.
Note
If the Issue complexity field is changed for an issue, the Total capacity is also updated.

To delete an issue linked to a sprint: in the Linked issues tab of the sprint, click on for the desired issue.
Note
If the Issue complexity was filled in for the deleted issue, the Total capacity is updated.

When a sprint is started, it means the sprint is in progress and the linked issues are being processed.
To start a sprint, click on Start sprint from the sprint's main tab.
When a sprint is started:
- The Status field is changed to Started.
- The start date and the employee who started the sprint are displayed at the right of the Started status.
- The linked issues cannot be changed once the sprint is started (unless the user has the appropriate rights).
To cancel the start of a sprint, open the Edit menu from the sprint screen then click Cancel sprint start. The sprint goes back to its previous status, before it was started.

Note
A sprint can only be completed after it has been started.
When a sprint is completed, it means the sprint cannot be used anymore and the linked issues have been resolved (or linked to new sprints).
To complete a started sprint, click on End the sprint from the sprint's main tab.
When a sprint is completed:
- The Status field is changed to Completed.
- The completion date and the employee who completed the sprint are displayed at the right of the Completed status.
- The sprint and the linked issues cannot be modified.
To cancel the completion of a sprint, open the Edit menu from the sprint screen then click Cancel sprint completion. The sprint goes back to its previous status, before it was completed.

Important
Deleting a sprint cannot be reversed.
Note
A sprint cannot be deleted if it is linked to issues.
1 | From the desired sprint, click on |
2 | Confirm the deletion. |
The sprint is deleted.