Allow required approvals from different groups to same changeset
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Proposal
As a member of an organisation with thousands of users, multiple compliances and strict processes created around software integration,
I want to be able to set required approvals from different users or teams towards the same changeset,
so I can make sure that changes to critical components are approved not only by any eligible approver, but by each one of (or at minimum one of each group) that I define.
Example
A real use case example can be seen at 378181.
My organisation has several use cases where some key people or teams are required to approve a given changeset. With the current approval rules and CODEOWNERS, it's only possible to specify what are the eligible approvers and how many approvals are required, but there's no way to require at leat one approval from each eligible approver (person) or team.
With the current rules, if I require 3 approvals from 3 teams, this means any 3 approvals are valid, even if they all come from the same team.