Direct-transfer placeholder users: list Enterprise users for re-assignment on gitlab.com

Release notes

Direct-transfer placeholder users drop-down containing only Enterprise users.

Problem to solve

Direct-transfer placeholder users mapping feature offers a drop-down list of users for re-assignment.

This list shows all active users of the destination instance. On gitlab.com this is millions of users.

For customers using SCIM, usernames of destination users are not necessarily known for the reassigning Owner; when SCIM provisioning happens, the (source) usernames might be created with suffixes, to make them unique, and so in the dropdown, we get e.g. 5 usernames, so it’s hard to know which user is the correct one.

To limit human error and reduce the blast radius of potential mistakes this list should be narrowed down when possible.

In case of direct-transfer imports to gitlab.com, where the importing group is under a Premium or Ultimate license, we have the Enterprise users list available to offer for user re-assignment.

This list assumes only users that have already been onboarded/provisioned on gitlab.com and should therefore be the default selection but not enforced.

Proposal

Enterprise users are tied to (claimed by) a top-level group. It's a Premium+ feature.

If the top-level group, where the groups/projects imported, uses the gitlab.com Enterprise users feature, limit the placeholder users drop-down list to only Enterprise users present under the top-level group.

As for upload with CSV - currently the CSV behaviour relies on the limits coded into the reassignment service, so in the backend.

We want to make sure that where the groups/projects imported, uses the gitlab.com Enterprise users feature, CSV reassignment disallows for reassigning to a user outside of that scoped user group.

Intended users

Feature Usage Metrics

N/A

Does this feature require an audit event?

N/A

Link the doc and describe what is wrong with it.