<p>I don't believe there is any native functionality to help assist in this, and that this relationship will have to be modeled external to GitLab. I've opened this issue for clarity,</p>
<p><a href="https://gitlab.com/gitlab-org/gitlab/-/issues/365887" rel="nofollow noreferrer">https://gitlab.com/gitlab-org/gitlab/-/issues/365887</a></p>

CC BY-SA 4.0
2022-06-21T17:17:26.350Z
2022-06-21T17:17:26.350Z
Evan Carroll
<p>My company has the notion of a Senior Tier of developers. These developers are dispersed amongst development teams. Then we assign the Senior Developers from one team to assess the contribution from a different team they were assigned.</p>
<p>Let's say I have a project <code>foo</code> and for <code>foo</code>, I want</p>
<ul>
<li><code>SeniorBarGroup</code> to review PRs to <code>BazGroup</code>, and</li>
<li><code>SeniorBazGroup</code> to review PRs to <code>QuzGroup</code></li>
</ul>
<p>Is this workflow possible in GitLab?</p>

CC BY-SA 4.0
2022-06-21T14:10:21.400Z
What about CO - https://docs.gitlab.com/ee/user/project/code_owners.html
Kyslik
CC BY-SA 4.0
2022-06-21T15:34:55.033Z
@Kyslik Right from the get go, that doesn't sound like what I want (I may be missing something). _"Code Owners define who owns specific files or directories in a repository."_. That's what everyone does. We don't have "code owners" at $work though. We have team owners. Two senior devs owns the contributions of another team, regardless of files or directories.
Evan Carroll
CC BY-SA 4.0
2022-06-21T16:44:04.763Z
I think neither GH or GL support what you want. Even if you automate and "request" review from correct teams (using API or GraphQL), GL won't enforce it the same way how CO works.
Kyslik
CC BY-SA 4.0
2023-07-16T21:02:16.787Z
According to this [source](https://devops.stackexchange.com/questions/16177/does-gitlab-support-assigning-a-reviewer-based-on-the-contributor), there is no native functionality in GitLab to help assist in assigning a reviewer based on the contributor. However, you can model this relationship external to GitLab.
Baft Tabaku
<gitlab><pipeline><code-review>
Does GitLab support assigning a reviewer based on the contributor?
Evan Carroll
# Does GitLab support assigning a reviewer based on the contributor?

(Asked by: username_0 on 2022-06-20)

My company has the notion of a Senior Tier of developers. These developers are dispersed amongst development teams. Then we assign the Senior Developers from one team to assess the contribution from a different team they were assigned.

Let's say I have a project `foo` and for `foo`, I want

* `SeniorBarGroup` to review PRs to `BazGroup`, and
* `SeniorBazGroup` to review PRs to `QuzGroup`

Is this workflow possible in GitLab?

**Tags:** gitlab, pipeline, code-review

> **Comments:**
> **username_1**: What about CO - https://docs.gitlab.com/ee/user/project/code_owners.html  
> **username_0**: @username_1 Right from the get go, that doesn't sound like what I want (I may be missing something). _"Code Owners define who owns specific files or directories in a repository."_. That's what everyone does. We don't have "code owners" at $work though. We have team owners. Two senior devs owns the contributions of another team, regardless of files or directories.  
> **username_1**: I think neither GH or GL support what you want. Even if you automate and "request" review from correct teams (using API or GraphQL), GL won't enforce it the same way how CO works.  
> **username_2**: According to this [source](https://devops.stackexchange.com/questions/16177/does-gitlab-support-assigning-a-reviewer-based-on-the-contributor), there is no native functionality in GitLab to help assist in assigning a reviewer based on the contributor. However, you can model this relationship external to GitLab.  

---

## 1 answers

### Answer by username_0 on 2022-06-21. Score: 0 | Accepted answer

I don't believe there is any native functionality to help assist in this, and that this relationship will have to be modeled external to GitLab. I've opened this issue for clarity,

<https://gitlab.com/gitlab-org/gitlab/-/issues/365887>


---

