- View the iterations list
- Create an iteration
- Edit an iteration
- Add an issue to an iteration
- View an iteration report
- Disable iterations
- Introduced in GitLab Starter 13.1.
- It was deployed behind a feature flag, disabled by default.
- Became enabled by default on GitLab 13.2.
- It’s enabled on GitLab.com.
- It’s able to be enabled or disabled per-group.
- It’s recommended for production use.
- For GitLab self-managed instances, GitLab administrators can opt to disable it.
Iterations are a way to track issues over a period of time. This allows teams to track velocity and volatility metrics. Iterations can be used with milestones for tracking over different time periods.
For example, you can use:
- Milestones for Program Increments, which span 8-12 weeks.
- Iterations for Sprints, which span 2 weeks.
In GitLab, iterations are similar to milestones, with a few differences:
- Iterations are only available to groups.
- A group can only have one active iteration at a time.
- Iterations require both a start and an end date.
- Iteration date ranges cannot overlap.
To view the iterations list, in a group, go to Issues > Iterations. From there you can create a new iteration or click an iteration to get a more detailed view.
To create an iteration:
- In a group, go to Issues > Iterations.
- Click New iteration.
- Enter the title, a description (optional), a start date, and a due date.
- Click Create iteration. The iteration details page opens.
To edit an iteration, click the three-dot menu () > Edit iteration.
To learn how to add an issue to an iteration, see the steps in Managing issues.
You can track the progress of an iteration by reviewing iteration reports. An iteration report displays a list of all the issues assigned to an iteration and their status.
To view an iteration report, go to the iterations list page and click an iteration’s title.
Burndown charts help track completion progress of total scope, and burnup charts track the daily total count and weight of issues added to and completed in a given timebox.
GitLab Iterations feature is deployed with a feature flag that is enabled by default.
GitLab administrators with access to the GitLab Rails console
can disable it for your instance.
:group_iterations can be enabled or disabled per-group.
To enable it:
# Instance-wide Feature.enable(:group_iterations) # or by group Feature.enable(:group_iterations, Group.find(<group ID>))
To disable it:
# Instance-wide Feature.disable(:group_iterations) # or by group Feature.disable(:group_iterations, Group.find(<group ID>))