<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=538132) </details> <!--IssueSummary end--> <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> Creating this feature proposal on behalf of a ~"GitLab Ultimate" [customer](https://gitlab.lightning.force.com/lightning/r/Account/0018X0000365ESfQAM/view) (internal link) who reported this concern on a [support ticket](https://gitlab.zendesk.com/agent/tickets/621959)(internal link) ### Context When importing a project on GitLab, since 17.4 (with feature flag, later enabled in 17.7/8), if the project [imports collaborators](https://docs.gitlab.com/user/project/import/#user-contribution-and-membership-mapping), it results in [placeholder users](https://docs.gitlab.com/user/project/import/#placeholder-users) being created. To remove these users, it requires [contributions and memberships to be reassigned](https://docs.gitlab.com/user/project/import/#reassign-contributions-and-memberships). ### Proposal To add an option that would allow for projects imported from sources that create placeholder users (GitHub, Bitbucket Server & Gitea) to not create placeholder users and instead assign all contributions to the non-functional `Import User`. ### Why? It can be beneficial for certain scenarios to not create placeholder users when importing projects from other sources. In its current state, if a user does not wish to re-assign placeholder users after an import, they are left with numerous placeholder users on their instance/group. Relevant docs: https://docs.gitlab.com/user/project/import/#user-contribution-and-membership-mapping <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> <!-- Label reminders Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->