Approval roles
Description
Some projects may require approvals in different areas, for example from both a security perspective, a UX perspective and a technical perspective. Today we may solve this by adding one person from each of these roles to the approval group and require that everyone approves the MR. The issue with this approach is that it makes the approval process highly dependent on individuals; if someone is unavailable (sick, vacation, etc) the MR will not be approved. It is much more preferred to allow any, say, security technician to approve the MR from a security perspective, and so on.
Proposal
Allow us to specify a number of roles and assign team members to those roles. Then extend the approval process to allow us to specify the different types of roles that must approve a merge request.