<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Label this issue](https://contributors.gitlab.com/manage-issue?action=label&projectId=278964&issueIid=608350) </details> <!--IssueSummary end--> ## Summary Roll out Vue 3 (via `@vue/compat`) for the three work item Settings page entrypoints currently behind the `vue3_migrate_work_item_settings` feature flag. 🗂️ The pages in scope are: | Entrypoint | Page | | :--- | :--- | | `pages.groups.settings.work_items.show` | Group work item settings | | `pages.projects.settings.work_items` | Project work item settings | | `pages.admin.application_settings.work_item` | Admin work item application settings | Part of [Vue 3 migration: Settings entry points](https://gitlab.com/gitlab-org/gitlab/-/work_items/608110), which belongs to [Vue 3 migration: Project management entry points](https://gitlab.com/groups/gitlab-org/-/work_items/23066). - DRI: @deepika.guliani - Team Slack channel: `#vue3_migration` > [!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? The blast radius is limited to the three work item settings pages listed above. 🎯 No other page reads this flag, and no data is written differently under either bundle. Worth knowing: a page entry also pulls in its ancestor entrypoints, so on these three pages the shared settings apps mounted by the ancestors run under Vue 3 too. In practice that means the settings search box (`~/search_settings`), deploy tokens (`~/deploy_tokens`), and on the admin page `~/vue_alerts`. Those apps stay on Vue 2 everywhere else, since the flag only renames these three entries. The `@vue/compat` layer renders the existing Vue 2 components under the Vue 3 runtime, so disabling the flag immediately serves the Vue 2 bundle again with no data impact. Watch for rendering regressions in the settings forms, most notably custom status and custom field configuration, and for console warnings emitted by `@vue/compat`. ## Rollout Run all production `/chatops` in [`#production`](https://gitlab.slack.com/archives/C101F3796) and cross-post the results to `#vue3_migration`. 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 vue3_migrate_work_item_settings 50 --actors --dev --pre --staging --staging-ref /chatops gitlab run feature set vue3_migrate_work_item_settings true --dev --pre --staging --staging-ref ``` **Production** — percentage rollout (wait ≥15 min between steps, watch dashboards): ``` /chatops gitlab run feature set vue3_migrate_work_item_settings <percentage> --actors ``` Or target specific actors instead: ``` /chatops gitlab run feature set --project=gitlab-org/gitlab,gitlab-org/gitlab-foss vue3_migrate_work_item_settings true /chatops gitlab run feature set --group=gitlab-org,gitlab-com vue3_migrate_work_item_settings true /chatops gitlab run feature set --user=deepika.guliani vue3_migrate_work_item_settings 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). - [ ] Flip all three `vue3_migration.yml` files to `status: migrated` and remove the `feature_flag` line - [ ] Delete `ee/config/feature_flags/beta/vue3_migrate_work_item_settings.yml` - [ ] Tick the three entrypoints in [#608110](https://gitlab.com/gitlab-org/gitlab/-/work_items/608110) and close it ``` /chatops gitlab run release check <merge-request-url> <milestone> /chatops gitlab run feature delete vue3_migrate_work_item_settings --dev --pre --staging --staging-ref --production ``` ## Rollback ``` /chatops gitlab run feature set vue3_migrate_work_item_settings false # production /chatops gitlab run feature set vue3_migrate_work_item_settings false --dev --pre --staging --staging-ref # non-production /chatops gitlab run feature delete vue3_migrate_work_item_settings --dev --pre --staging --staging-ref --production # remove entirely ```