Groups inheritance for approvals
Groups inheritance for approvals
Group's membership inheritance is not applied to define the list of approvers on a merge request.
Steps to reproduce
You create a group 1 with user A and user B. You create a sub group 2 with user C and user D. You create a project "123" in group 2.
This means that A, B, C, D has access to project 123.
User C creates a merge request in project 123 and select group 2 as the approval group.
What is the current bug behavior?
Only user D is listed as a potential approver.
What is the expected correct behavior?
I would expect to see user A, B, D as potential approvers to that merge request (if they have the correct membership rights of course).
If for example user B doesn't have enough rights for the merge request (developer only at the group A level), I would expect to not have it in the list of approvers.