Test a new look for epics
- Introduced in GitLab 17.2 with several feature flags. Disabled by default. This feature is an experiment.
- Listing epics using the GraphQL API introduced in GitLab 17.4.
- Enabled on GitLab.com in GitLab 17.6.
We’re working on changing how epics look by migrating them to a unified framework for work items to better meet the product needs of our Agile Planning offering.
For more information, see epic 9290 and the following blog posts:
- First look: The new Agile planning experience in GitLab (June 2024)
- Unveiling a new epic experience for improved Agile planning (July 2024)
Feature flags
To try out this change on GitLab self-managed, enable the following feature flags. Because this is an experimental feature, we strongly advise to enable the feature flags on a new group that does not contain any critical data.
Flag | Description | Actor | Status | Milestone |
---|---|---|---|---|
work_item_epics
|
Consolidated flag that contains all the changes needed to get epic work items to work for a given group. | Group | Required | 17.2 |
work_items_rolledup_dates
|
Calculates the start and due dates in a hierarchy for work items. | Group | Required | 17.2 |
epic_and_work_item_associations_unification
|
Delegates other epic and work item associations. | Group | Required | 17.2 |
Feedback
If you run into any issues while trying out this change, you can use feedback issue to provide more details.