Manage MR approvers from the GitLab group level.
Problem to solve
Allow the ability to manage a set of MR approvers at a GitLab group level instead of per project. All projects within the group would utilize the approvers defined at the group level with the ability to override (at the project level) if a different approver should be defined.
Target audience
-
Delaney, Development Team Lead, https://design.gitlab.com/research/personas#persona-delaney
-
Devon, DevOps Engineer, https://design.gitlab.com/research/personas#persona-devon
-
Sidney, Systems Administrator, https://design.gitlab.com/research/personas#persona-sidney
-
Sam, Security Analyst, https://design.gitlab.com/research/personas#persona-sam
Further details
Proposal
What does success look like, and how can we measure that?
Similar to being able to set-up a project level approver default, you would set that at the group level. Project can override group and an individual MR can override either project or group. The current method of creating the approval at the project level can be re-used for group.
What is the type of buyer?
(Which leads to: in which enterprise tier should this feature go see https://about.gitlab.com/handbook/product/pricing/#four-tiers )
I think this could initially be limited to Premium or above -- or even Ultimate.