Skip to content

Feature flags requiring attention for group::incubation - 2025-10-01

This is a group level feature flag report containing feature flags that should be evaluated or need action.

Feature flag trends can be found in this dashboard.

A feature flag is considered end-of-life when it has existed in the codebase for longer than the prescribed lifespan based on feature flag type.

Feature flags needing action

These flags are approaching end-of-life in the next milestone.

Feature flag Milestone added End of life milestone Enabled by default? Rollout issue

Please take action on these feature flags by performing one of the following options:

  1. Enable the feature flag by default and remove it.
  2. Convert it to an instance, group, or project setting.
  3. Revert the changes if it's still disabled and not needed anymore.

Feature flags overdue

These flags have reached their maximum lifespan.

Feature flag Milestone added End of life milestone Enabled by default? Rollout issue
feature_flag_state_logs
ops | Introduced by | No feature issue | GitLab.com state changes
%14.6 %15.6 [Feature flag] Rollout of `feature_flag_state_l... (gitlab-org/gitlab#345888 - closed) • Eduardo Bonet
cloudseed_aws
development | Introduced by | No feature issue | GitLab.com state changes
%15.10 %16.4 [Feature flag] Rollout of `cloudseed_aws` (gitlab-org/gitlab#395777) • Unassigned

Please review these feature flags to determine if they are able to be removed entirely.


This report is generated from feature-flag-alert project by https://gitlab.com/gitlab-org/quality/toolbox/-/jobs/11559330452.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information