Set Experiments Checkbox to 'false' when 'never_on' is selected in Duo Availability
What does this MR do and why?
This MR covers the following Issue:
- #480400 (closed) Follow-up from "Ban AI Duo Experiment Beta Features Checkbox"
In a recent MR, a discussion was had around how the experiment_features_enabled checkbox should behave when never_on is selected. It was decided to have this setting handled on the backend to ensure when never_on is checked, then experiment_features_enabled should also be set to false.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
| Before | After |
|---|---|
 |
 |
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Group Settings - Experiment & Beta Settings
- Log into your GDK/Local Instance (Make sure you are in SAAS mode and on the Ultimate tier)
- Go to the top level Group Settings (that has the Ultimate license set): Group > Settings > General > GitLab Duo
- Check Use experiment and beta GitLab Duo features under GitLab experiment and beta features
- Click Save changes
- Validate that the checkbox is checked.
- Select Never on under Availability
- Click Save changes
- Validate that the checkbox is unchecked
Admin Settings - Experiment & Beta Settings
- Log into your GDK/Local Instance (Make sure you are in Standalone Mode or .com)
- Go to Admin Settings (that has the Ultimate license set): Admin > Settings > General > GitLab Duo
- Check Use experiment and beta GitLab Duo features under GitLab experiment and beta features
- Click Save changes
- Validate that the checkbox is checked.
- Select Never on under Availability
- Click Save changes
- Validate that the checkbox is unchecked
Edited by Lindsey Shelton