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)
Enable and disable the new look for epics
To try out this change on GitLab self-managed, run the following Rake task.
The task performs a database verification to ensure data consistency and might take a few minutes.
If the consistency check passes, the Rake task enables the work_item_epics
feature flag.
If the check fails, the feature flag is not enabled. Inconsistencies are logged in the epic_work_item_sync.log
file.
Failed background migrations or invalid imports can cause data inconsistencies. These inconsistencies will be resolved when work item epics become generally available.
To enable:
# omnibus-gitlab
sudo gitlab-rake gitlab:work_items:epics:enable
# installation from source
bundle exec rake gitlab:work_items:epics:enable RAILS_ENV=production
To disable:
# omnibus-gitlab
sudo gitlab-rake gitlab:work_items:epics:disable
# installation from source
bundle exec rake gitlab:work_items:epics:disable RAILS_ENV=production
Feedback
If you run into any issues while trying out this change, you can use feedback issue to provide more details.