3.3 KiB
| type | stage | group | info |
|---|---|---|---|
| reference | Plan | Project Management | To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers |
Iterations (STARTER)
- Introduced in GitLab Starter 13.1.
- It's deployed behind a feature flag, disabled by default.
- It's disabled on GitLab.com.
- It's able to be enabled or disabled per-group
- It's not recommended for production use.
- To use it in GitLab self-managed instances, ask a GitLab administrator to enable it. (CORE ONLY)
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.
View the iterations list
To view the iterations list, in a group, go to {issues} Issues > Iterations. From there you can create a new iteration or click an iteration to get a more detailed view.
Create an iteration
NOTE: Note: A permission level of Developer or higher is required to create iterations.
To create an iteration:
- In a group, go to {issues} 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.
Enable Iterations (CORE ONLY)
GitLab Iterations feature is under development and not ready for production use.
It is deployed behind a feature flag that is disabled by default.
GitLab administrators with access to the GitLab Rails console
can enable 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>))