Feature flags requiring attention for group::database frameworks - 2025-09-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:
- Enable the feature flag by default and remove it.
- Convert it to an instance, group, or project setting.
- 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 |
|---|---|---|---|---|
query_analyzer_gitlab_schema_metrics ops | Introduced by | No feature issue | GitLab.com state changes |
%14.5 | %15.5 | ||
reset_column_information_on_statement_invalid ops | Introduced by | No feature issue | GitLab.com state changes |
%16.1 | %17.1 | ||
loose_foreign_keys_turbo_mode_ci ops | Introduced by | No feature issue | GitLab.com state changes |
%16.4 | %17.4 | ||
loose_foreign_keys_turbo_mode_main ops | Introduced by | No feature issue | GitLab.com state changes |
%16.4 | %17.4 |
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/11201524457.