Test a new look for epics
-
Introduced in GitLab 17.2 with a flag named
work_item_epics
. Disabled by default. This feature is in beta. - Listing epics using the GraphQL API introduced in GitLab 17.4.
- Enabled on GitLab.com in GitLab 17.6.
- Enabled by default on self-managed and GitLab Dedicated in GitLab 17.7.
We have changed 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)
Troubleshooting
If you run into any issues while navigating your data in the new experience, there are a couple of ways you can try to resolve it.
Access the old experience
You can temporarily load the old experience by editing URL to include force_legacy_view=true
parameter,
for example, https://gitlab.com/groups/gitlab-org/-/epics/9290?force_legacy_view=true
. Use this parameter to do any comparison
between old and new experience to provide details while opening support request.
Disable the new experience
We don’t recommend disabling this change, because we’d like your feedback on what you don’t like about it.
If you have to disable the new experience to unblock your workflow, disable the work_item_epics
feature flag.
Feedback
If you run into any issues while trying out this change, you can use feedback issue to provide more details.