Allow distinct approvers for merge rules
Problem to solve
Our current (manual) process is we require one code review and one functional review, these need to be distinct i.e. the same person cannot approve both the functionality and code.
This is one specific feature addressing #36038 (closed)
Release Manager, Developers
Having the ability to approve a specific rule is a precursor to this requirement as outlined in ticket #36485
We would like a configuration option to enforce each approval to be by a distinct approver across all rules for a single merge request.
What does success look like, and how can we measure that?
If any rule for this merge has been approved by a user they are no longer able to approve any other rules on this merge request even if they they are assigned to them.
What is the type of buyer?