<!-- Title suggestion: [FF] `<feature-flag-name>` -- <short description> --> ## Summary Redirects relative-position **writes** from `issues.relative_position` to `work_item_positions.relative_position` (the new source of truth). Introduced in !250395. Part of &amp;23222 / #612911. Roll out [the feature](<feature-issue-link>) currently behind the `<feature-flag-name>` feature flag. - DRI: @vjain-gl - Team Slack channel: `#g_planning-views` > [!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) ## Prerequisites (must complete before enabling) The write cutover lands in slices behind the flag; it must stay **off** until all of these are done, or `issues.relative_position` and `work_item_positions` diverge (some paths write one column, some the other, while reads come from `work_item_positions`): - [ ] Redirect **all** position write paths to `work_item_positions` (rebalancing !250395; sibling-shift !253169; still to do: the core move path in `Mover`/`ItemContext`, and `move_nulls`). A partial cutover diverges the two columns and breaks move/placement logic. - [ ] Make the rebalance decision read the source of truth: `Issues::BaseService#rebalance_if_needed` and `Issues::PlacementWorker` (`max_by(&:relative_position)`) currently read `issues.relative_position`; with the flag on they must read `work_item_positions`, or a rebalance never clears the value that scheduled it and loops (raised by @mdangelo6 on !250395). - [ ] Audit other direct readers of `issues.relative_position` used for decisions/data (e.g. the work item data-sync copy handler) and route them to the source of truth. - [ ] Remove the test-only global stub `spec/support/work_item_positions_write_flag.rb` (it defaults the flag off across the suite) once the above are done. ## What could go wrong? <!-- Optional but recommended: blast radius, data-loss risk, and the dashboard(s) you'll watch on https://dashboards.gitlab.net. Delete if not applicable. --> ## 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 <feature-flag-name> 50 --actors --dev --pre --staging --staging-ref /chatops gitlab run feature set <feature-flag-name> true --dev --pre --staging --staging-ref ``` **Production** — percentage rollout (wait ≥15 min between steps, watch dashboards): ``` /chatops gitlab run feature set <feature-flag-name> <percentage> --actors ``` Or target specific actors instead: ``` /chatops gitlab run feature set --project=gitlab-org/gitlab,gitlab-org/gitlab-foss <feature-flag-name> true /chatops gitlab run feature set --group=gitlab-org,gitlab-com <feature-flag-name> true /chatops gitlab run feature set --user=<gitlab-username-of-dri> <feature-flag-name> true ``` ## 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 ## Cleanup Remove the flag once [deemed stable](https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/feature-flag-lifecycle/#feature-flag-lifecycle) — see [cleaning up](https://docs.gitlab.com/development/feature_flags/controls/#cleaning-up). Track it here, or open a follow-up [Feature Flag Cleanup issue](https://gitlab.com/gitlab-org/gitlab/-/work_items/new?description_template=Feature%20Flag%20Cleanup). Remove the flag and its YAML definition from the codebase, then: ``` /chatops gitlab run release check <merge-request-url> <milestone> /chatops gitlab run feature delete <feature-flag-name> --dev --pre --staging --staging-ref --production ``` ## Rollback ``` /chatops gitlab run feature set <feature-flag-name> false # production /chatops gitlab run feature set <feature-flag-name> false --dev --pre --staging --staging-ref # non-production /chatops gitlab run feature delete <feature-flag-name> --dev --pre --staging --staging-ref --production # remove entirely ``` <!-- Uncomment the appropriate type label /label ~"type::feature" ~"feature::addition" /label ~"type::maintenance" /label ~"type::bug" -->