## Summary This issue is to roll out the feature on production that is currently behind the `no_duo_classic_for_duo_core_users` feature flag. Related MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/214718 Related Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/581229 ## Owners - Most appropriate Slack channel to reach out to: `#g_duo_chat` - Best individual to reach out to: @tbulva ## Expectations ### What are we expecting to happen? - Duo Core users will no longer have access to classic Duo Chat mode - The chat mode toggle will be hidden for Duo Core users - Duo Core users will be automatically switched to agentic mode - Duo Pro users will continue to have access to both classic and agentic modes ### What can go wrong and how would we detect it? - Duo Core users might experience unexpected behavior if they were actively using classic mode - The mode toggle might not hide correctly for Duo Core users - Agentic mode might not activate properly for Duo Core users **Detection:** - Monitor error rates in Duo Chat interactions - Check for increased support tickets related to Duo Chat access - Monitor Sentry for any JavaScript errors related to chat mode switching ## Rollout Steps See the full rollout template at: https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20Flag%20Roll%20Out.md ### Rollout on non-production environments - [ ] Deploy the feature flag at 50% with `/chatops run feature set no_duo_classic_for_duo_core_users 50 --actors --dev --pre --staging --staging-ref` - [ ] Monitor that the error rates did not increase - [x] Enable globally on non-production with `/chatops run feature set no_duo_classic_for_duo_core_users true --dev --pre --staging --staging-ref` - [x] Verify that the feature works as expected ### Specific rollout on production - [ ] Enable for specific actors first (e.g., internal users) - [ ] Verify that the feature works for the specific actors ### Preparation before global rollout - [x] Set a milestone to this rollout issue - [x] Check if change management issue is needed - [x] Ensure availability for at least 2 hours after feature flag updates - [x] Ensure documentation exists - [x] Notify support channels if needed ### Global rollout on production - [x] Incrementally roll out the feature on production - [x] Monitor dashboards between each step - [x] After 100% enabled, wait at least one day before cleanup ### Release the feature - [ ] Create MR to remove the feature flag from codebase - [ ] Clean up feature flag from all environments - [ ] Close this rollout issue