Discussion around User suggestion across the UI and permission assignment

Hello everyone, to reduce the workload related to user and permission management, and to have a cleanest report of permissions we use only groups to allocate permission across the GitLab istance.

We have a structure of groups/subgroups/projects for our coding and a structure for creating groups of people that we will use for wide notifications and for permission assignment.

Here a simple schema to clarify the permission model.

graph TD;
  G[GitLab Istance]-->P[People];
  G-->C[Code];
  P-->D[Devs];
  P-->O[Ops];
  P-->S[Security];
  P-->M[Project Managers];
  C-->P1[Project Alpha];
  C-->P2[Project Beta];
  C-->P3[Project Gamma];

In People there is only subgroups containing members, never a project.

In Code we have the typical projects containing code, issues, documentation, registries...

i.e. Project Alpha will have the following permission

• Owner: Individual
• Maintainer: Devs Group
• Reporter: Project Managers Group etc etc

This approach works like a charm and it's really sustainable compared to single user assignment, but we are expecting a few undesired behaviors:

• If a group contains another group, the childs will not inherit the permission assigning the parent group to a project
• You are not able to get tag suggestion for a user that has visibility but it is not part of the project (i.e. an internal project), the target user is able to view and contribute, and if you manually tag the user, it works, but you get no suggestion for the correct name
• If you have a board and you want to use a column to show assignees, you are not able to select from the list users that are not directly assigned to the project and that can access through a group permission.

What do you think about this use case? May you evaluate to reduce the drift describe here and/or provide alternative path for a similar user journey?

Thanks

(we are a direct Premium Customer, an Open Reseller and a Professional Service Partner)