Project Import User Mapping Whitelist via Access Token
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
Currently with a project import the user mapping is not made if the importing user is not an admin on the instance.
Further details
The class Gitlab.ImportExport.MembersMapper prevents non-admin users to map the users here:
https://gitlab.com/gitlab-org/gitlab-ce/blob/master/lib/gitlab/import_export/members_mapper.rb#L5
This is especially a problem if you're migrating from a private instance to GitLab.com where you can't obtain an admin account.
Proposal
If there were an alternate way to authenticate the users (assignees, comment authors etc.), those users could be whitelisted and the import could correctly map the users on the new instance.
I propose that given a map of users and access tokens from the new instance could be provided to the import API Endpoint. Therefore the importer would be authorized to create entries (issues, comments etc.) in the name of the given user.
What does success look like, and how can we measure that?
Given a map of old username, new username & access token we can migrate a project to an instance without admin rights and preserve the ownerships.