<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=456799) </details> <!--IssueSummary end--> <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal we would like to see support more flexible codeowner approval rules. example structure - shared_sub_project - sub_project 1 (devs 1,2,3) - sub_project2 (devs 4,5,6) - sub_project 3 (devs 7,8,9) We have for example a monorepo with 3 subprojects, each subproject has 3 devs. The subprojects share another subproject. We want to enforce code quality by having at least two different projects approve changes on the shared project. right now we have a rule like ``` [shared maintainers][2] dev1 dev4 dev7 shared_sub_project ``` But with this rule we are often blocked by the need of two of three specific devs to approve the mr. If we could have groups instead this would be much more efficient. so we suggest something like ``` [shared maintainers][2] (dev1,dev2,dev3), (dev4,dev5,dev6), (dev7,dev8,dev9) shared_sub_project ``` <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> <!-- Label reminders Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->