Skip to content

Draft: Ban AI Group and Admin Settings Section

Lindsey Shelton requested to merge ban-ai-duo-settings-admin-group-form into master

What does this MR do and why?

This MR covers the following Issues:

The purpose of this MR is to introduce the new section Duo Availability in both Admin and Group Settings. This will be an update of the existing Cascading checkboxes/Experimental checkbox in Permission and group settings in Groups and the checkboxes that exist in Admin Settings.

Please note, this feature will evolve again in the future. All documentation relating to this Issue will be in this MR.

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
Screenshot_2024-08-04_at_10.15.33_PM Screenshot_2024-08-04_at_10.20.28_PM

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Group Settings - Duo Availability

  1. Log into your GDK/Local Instance (Make sure you are in SAAS mode and on the Ultimate tier)
  • It is assumed that the 'GitLab Duo experiment and beta features' checkbox is selected
  1. Test 'On by default'
  • Go to the top level Group Settings (that has the Ultimate license set): Group > Settings > General > GitLab Duo.
  • Under 'Availability' select 'On by default'.
  • Select 'Save changes'
  • Go to subgroup level Group Settings: Group > Settings > General > GitLab Duo > Availability.
  • Validate 'On by default.' is checked
  • Validate Duo Features are enabled (you can go to a Project Issue and see if Issue description generation is available as an example)
  • Go to subgroup level Group Settings: Group > Settings > General > GitLab Duo > Availability.
  • Validate 'On by default.' is checked. (Optional: You may change this to another radio selection and it will not impact the parent top-level group value)
  • (Optional) Test settings the above again if there is a subgroup available.
  1. Test 'Off by default'
  • Go to the top level Group Settings (that has the Ultimate license set): Group > Settings > General > GitLab Duo.
  • Under 'Availability' select 'Off by default'.
  • Validate warning message appears.
  • Select 'Save changes'
  • Validate warning message is gone.
  • Go to subgroup level Group Settings: Group > Settings > General > GitLab Duo > Availability.
  • Validate 'Off by default.' is checked. (Optional: You may change this to another radio selection and it will not impact the parent top-level group value)
  • Validate Duo Features are disabled (you can go to a Project Issue and see if Issue description generation is not available as an example)
  • (Optional) Test settings the above again if there is a subgroup available.
  1. Test 'Never on'
  • Go to the top level Group Settings (that has the Ultimate license set): Group > Settings > General > GitLab Duo.
  • Under 'Availability' select 'Never on'.
  • Validate warning message appears.
  • Select 'Save changes'
  • Validate warning message is gone.
  • Go to subgroup level Group Settings: Group > Settings > General > GitLab Duo > Availability.
  • Validate 'Never on.' is checked, that all 3 radio buttons are disabled, and that there is a popover lock icon next to 'Never on'
  • Validate Duo Features are disabled (you can go to a Project Issue and see if Issue description generation is not available as an example)

Group Settings - Experiment & Beta Settings

  1. Log into your GDK/Local Instance (Make sure you are in SAAS mode and on the Ultimate tier)
  2. Go to the top level Group Settings (that has the Ultimate license set): Group > Settings > General > GitLab Duo
  3. Validate "GitLab Duo experiment and beta features" section and checkbox exists.
  4. Go to a subgroup of the parent group you were testing.
  5. Go to the subgroup level Group Settings: Group > Settings > General > GitLab Duo.
  6. Validate "GitLab Duo experiment and beta features" section and checkbox do not exist.

Admin Settings - Duo Availability

  1. Log into your GDK/Local Instance (Make sure you are in Standalone Mode or .com)
  • It is assumed that the 'GitLab Duo preview features' checkbox is selected
  1. Test 'On by default'
  • Go to Admin Settings: Admin > Settings > General > GitLab Duo.
  • Under 'Availability' select 'On by default'.
  • Select 'Save changes'
  • Go to subgroup level Group Settings: Group > Settings > General > GitLab Duo > Availability.
  • Validate 'On by default.' is checked
  1. Test 'Off by default'
  • Go to Admin Settings: Admin > Settings > General > GitLab Duo.
  • Under 'Availability' select 'Off by default'.
  • Validate warning message appears.
  • Select 'Save changes'
  • Validate warning message is gone.
  1. Test 'Never on'
  • Go to Admin Settings: Admin > Settings > General > GitLab Duo.
  • Under 'Availability' select 'Never on'.
  • Validate warning message appears.
  • Select 'Save changes'
  • Validate warning message is gone.

Group Settings - Experiment & Beta Settings

  1. Log into your GDK/Local Instance (Make sure you are in Standalone Mode or .com)
  2. Go to Admin Settings (that has the Ultimate license set): Admin > Settings > General > GitLab Duo
  3. Validate GitLab Duo experiment and beta features section and checkbox exists.
Edited by Lindsey Shelton

Merge request reports