Yes — you can require approvals from a group instead of naming fixed individual reviewers.

Setup

In the target project's branch protection settings, set the review requirement to a group, for example:

• group(Reviewers) — one approval from any member of that group
• group(Reviewers):2 — two approvals from that group

See also:

• Code Review (section Reviewer Auto-Suggestion)
• Pull Request Approval

Behavior

When the requirement uses a group, OneDev auto-suggests the most appropriate members (based on commit history of the touched files) and assigns them as reviewers. Those assignees are notified by mail.

They are not permanently fixed:

• If the suggested person is unavailable, remove them on the pull request — OneDev will pick another suitable member from the group.
• You can also add other reviewers manually.

Limitation

There is no mode that leaves a pull request with no assigned reviewers while still enforcing “anyone from the group may approve.” Approvals are always tied to assigned reviewers; for group rules, the set of assignees is flexible and can be swapped as above.

If that still does not cover your workflow (e.g. you want zero auto-assignment / no mail until someone claims the review), please say so and we can treat it as a feature request.

Sadly this does not cover my workflow. I would like to have the pull requests open for taking when freshly created and anyone from that group can review them in addition to manually added reviewers that are then still needed for the pr to be merged.

Thanks for clarifying. That workflow is not supported today:

1. With a group review requirement, OneDev always auto-assigns suggested members (and notifies them). There is no “open for taking” mode that leaves a newly created PR with no reviewers until someone claims it.
2. Approvals that satisfy the group rule come from assigned reviewers. Other group members can review only after they are added as reviewers.
3. Manually added reviewers already must approve before merge (all non-excluded reviewers must approve).

So the gap is: keep group (and optional individual) review requirements, but skip auto-assignment so the PR stays claimable by any group member, while still requiring any manually added reviewers.

@robin — escalating as a feature request for optional “no auto-assign / claimable review” behavior on group review requirements.

This seems odd to me, as no one will be notified of such PR and no one will be actually responsible for it...

In this screenshot I am logged into an account which is not the pull request creator nor the required reviewer automatically set. Now I cannot review it because I do not have the permission to add myself as a reviewer and remove others. I do in fact have the ability with this user to review this pull request and then merge it if I was assigned to it. Which makes it impractical because I do not know if who will be able to first review a pull request I create and when I add multiple people all of them are required to merge it.

The screenshot matches current behavior, and it also means the earlier workaround (remove the suggested reviewer so OneDev picks someone else) does not work for this account.

Why this user cannot review

• Approve is available only if you are already an assigned reviewer. Being able to merge (Write Code) is not enough.
• Adding or removing reviewers requires Pull Request Management, or being the pull request submitter or an assignee. The default Code Writer role has Write Code but not Pull Request Management, so a capable reviewer cannot add themselves.

Workaround with current features

Grant Pull Request Management to the reviewer group (role settings, or the project authorization for that group). Members can then add themselves as reviewer. Once another eligible group member is assigned, they can remove the auto-suggested person if needed.

The pull request submitter can already change reviewers without that permission. Adding several people still requires all of them to approve before merge; that is by design.

Still not supported

A newly created pull request cannot stay unassigned so that any group member may approve it without being added first. Auto-suggestion and mail to the picked reviewers also cannot be turned off.

@robin — this is the same feature request as before, with the extra constraint that typical Code Writers cannot self-assign as reviewer.

Assigning a user does not mean that the user has to merge the PR. It only gives the user necessary permissions on the PR, and the actual responsibility is agreed upon in your team.

I would just really like for anyone of the reviewer group that is set on the required reviewers to be able to review it and merge it that was not specifically assigned to it. We work via a four eyes workflow. We trust each other in the code we want to merge but still require atleast one other person to look over it before merging which should be the person that has some time for it first and not anyone specifically.

@robin How are you planning to go forward with this?

Will support this for future versions, but cannot promise a schedule for now.