[gitlab.com] Duo Code Review: enable automatic review for multiple projects within namespace
Problem to solve
As an admin, I want to mass enable automatic reviews via Duo Code Review for all or most of my projects, so I can avoid the time required to manually enabling hundreds or thousands of individual projects.
Proposal
As a first iteration, provide a UI affordance at the group level using cascading settings, allowing a group admin to enable automatic review by Duo Code Review for all projects in the group.
MVC functionality
- Ability to enable all projects in a group.
- If all of Duo is disabled for a project, then enabling automatic review by Duo Code Review should effectively be a no-op.
- If a customer needs to enable some, but not all, projects in a group - they can use the project-level enablement setting that already exists.
- [Updated] If the group has automatic review enabled, then the project-level setting is default enabled but can be optionally disabled. This maintains consistency with existing cascading settings behavior where a child resource can override the parent.
- [Deprecated]
If the group has automatic review enabled, then the existing project-level setting is selected and disabled (i.e. cannot be disabled). We can potentially make this more flexible in a future iteration.
- [Deprecated]
Edited by 🤖 GitLab Bot 🤖