Direct transfer: Allow reassigning placeholder users to non-human accounts
Description
When importing projects using direct transfer
a placeholder user is created for any active, inactive, or bot user with imported contributions or memberships.
However
Bot user contributions and memberships on the source instance cannot be reassigned to bot users on the destination instance.
Currently, for non-human placeholder users i.e. bots and service accounts
You might choose to keep source bot user contributions assigned to a placeholder user.
In some cases, this may be a blocker, e.g. project protected branches unprotect_access_levels, where only the specified user can then unprotect the branch.
NOTE: There may be other cases, where creating a placeholder user for a non-human account configured for a feature on source, blocks the usage of the feature on destination.
Proposal
To prevent locking direct transfer imported project protected branches that had non-human accounts configured on source:
- Allow one (top-level group Owners) to reassign placeholder users to non-human accounts
- Acknowledge that this type of reassignment should not require approval, as non-human accounts cannot receive or approve emails
- (optional) add an additional (modal?) confirmation window as reassignment is automatic in this scenario, and cannot be cancelled
- Filter placeholder user reassignment drop-down list for non-human accounts that belong to the same top-level group