Enable automatic reviews by GitLab Duo setting missing from UI
Summary
The "Enable automatic reviews by GitLab Duo" checkbox has disappeared from Project and Group Merge Request settings.
Reported by @hlange4 - the setting was previously visible but is now gone.
Affects both GitLab team members with Duo Enterprise and non-team-member accounts with Duo Core.
Potentially related to commit 7355bea2 (Add routing logic for Duo Code Review between legacy and DAP flows) and feature flags duo_code_review_on_agent_platform and duo_code_review_dap_internal_users.
CC @kinsingh for investigation.
Steps to reproduce
Project Level
- Navigate to a project where you have Maintainer or Owner access
- Go to Settings > Merge requests
- Scroll to the Merge request approvals section
- Look for the "Enable automatic reviews by GitLab Duo" checkbox
- Observe: The checkbox is missing from the UI
Group Level
- Navigate to a group where you have Owner access
- Go to Settings > General
- Expand the Merge request approvals section
- Look for the "Enable automatic reviews by GitLab Duo" checkbox
- Observe: The checkbox is missing from the UI
Example Project
Any project or group with Duo Enterprise or Duo Core enabled.
What is the current bug behavior?
The "Enable automatic reviews by GitLab Duo" checkbox is not visible in either:
- Project Settings > Merge requests > Merge request approvals
- Group Settings > General > Merge request approvals
What is the expected correct behavior?
The "Enable automatic reviews by GitLab Duo" checkbox should be visible and configurable in both project and group merge request approval settings for users with appropriate Duo licenses (Duo Enterprise or Duo Core).
Relevant logs and/or screenshots
Output of checks
This issue affects GitLab.com (SaaS).
Results of GitLab environment info
N/A - GitLab.com SaaS
Results of GitLab application Check
N/A - GitLab.com SaaS
Possible fixes
Investigate the routing logic introduced in commit 7355bea2 and the feature flags:
duo_code_review_on_agent_platformduo_code_review_dap_internal_users
The visibility condition for the checkbox may have been inadvertently affected by these changes.