## Summary Roll out [the feature](https://gitlab.com/gitlab-org/gitlab/-/issues/606182) currently behind the `limit_labels_per_work_item` feature flag. - DRI: @daniyalAD - Team Slack channel: `#g_portfolio-planning` > [!note] > Process and guidance live in the docs — this issue is just the commands and a place to track the rollout. > "Rolling out" means incrementally enabling the flag on GitLab.com to validate stability — it is not the same as releasing the feature, which happens when the flag is removed. > [Feature flag controls](https://docs.gitlab.com/development/feature_flags/controls/) · [Feature flag lifecycle](https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/feature-flag-lifecycle/#feature-flag-lifecycle) ## What could go wrong? Introduced in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/253768 ("Limit the number of labels on a work item to 100"), enabled per top-level group (`resource_parent.root_ancestor` is the flag actor). - A workflow that legitimately adds more than 100 labels to a work item (issue, epic, or task) will start getting rejected with "Cannot add more than 100 labels to a work item." — surfaced as a REST 400, a GraphQL mutation error, or a failed `/label` quick action. - The limit is delta-only: work items already over 100 labels are unaffected for removals, they just can't gain more labels. - Merge requests are not gated by this flag. - No data-loss risk — nothing is deleted, existing labels are untouched. - Rollback is a simple flag disable; no follow-up cleanup needed. - Watch exceptions/events for `limit_labels_per_work_item:1` (links below) and API error rates on the issues/work items endpoints on https://dashboards.gitlab.net. ## Events - [Exceptions with limit_labels_per_work_item:1](https://log.gprd.gitlab.net/app/discover#/?_g=(time:(from:now-1d,to:now))&_a=(index:'7092c4e2-4eb5-46f2-8305-a7da2edad090',query:(language:kuery,query:'json.exception.feature_flag_states.keyword:%22limit_labels_per_work_item:1%22'),columns:!(json.exception.class,json.exception.message,json.extra.workflow_id,json.meta.caller_id),sort:!(!(json.time,desc)))) - [Events with limit_labels_per_work_item:1](https://log.gprd.gitlab.net/app/discover#/?_g=(time:(from:now-1d,to:now))&_a=(index:'7092c4e2-4eb5-46f2-8305-a7da2edad090',query:(language:kuery,query:'json.feature_flag_states:%22limit_labels_per_work_item:1%22'),columns:!(json.meta.caller_id,json.feature_flag_states),sort:!(!(json.time,desc)))) - [Error rate and other graphs by modifying the examples in the Visualization Library](https://log.gprd.gitlab.net/app/visualize#/?_g=h@358d019&s=FF%20Observability) Feature Flag events are only logged by default for feature flags marked for the current or future milestones. To enable while the feature flag is active, see https://docs.gitlab.com/development/feature_flags/#logging ## Rollout Run all production `/chatops` in [`#production`](https://gitlab.slack.com/archives/C101F3796) and cross-post the results to `#<slack-channel-of-dri-team>`. Background: [incremental rollout process](https://docs.gitlab.com/development/feature_flags/controls/#process), [feature actors](https://docs.gitlab.com/development/feature_flags/#feature-actors). **Non-production** ``` /chatops gitlab run feature set limit_labels_per_work_item 50 --actors --dev --pre --staging --staging-ref /chatops gitlab run feature set limit_labels_per_work_item true --dev --pre --staging --staging-ref ``` **Production** — percentage rollout (wait ≥15 min between steps, watch dashboards): ``` /chatops gitlab run feature set limit_labels_per_work_item <percentage> --actors ``` Suggested percentage steps: 10, 25, 50, 100, each at least 15 minutes apart while watching logs. Or target a specific actor instead. The flag actor is the root namespace, so only the `--group=` form applies here (there's no per-project or per-user actor for this flag): ``` /chatops gitlab run feature set --group=gitlab-org limit_labels_per_work_item true ``` Enable for `gitlab-org` first, then proceed with the percentage rollout above. ## Before global rollout Confirm the relevant gotchas before going to 100% — see [enabling a feature for GitLab.com](https://docs.gitlab.com/development/feature_flags/controls/#enabling-a-feature-for-gitlabcom): - [Docs + version history](https://docs.gitlab.com/development/documentation/feature_flags/) updated - [Breaking changes](https://docs.gitlab.com/development/documentation/release_notes/#deprecations-removals-and-breaking-changes) announced, if any - [Change management issue](https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/change-management/#feature-flags-and-the-change-management-process) opened, if required - [External API consumers](https://docs.gitlab.com/development/feature_flags/#do-not-use-feature-flags-in-external-api-consumers) handled with a fail-open mechanism, if applicable Once GitLab.com is at 100% and stable, follow up with an MR to set `default_enabled: true` for self-managed instances, then remove the flag.