Merge requests are owned by the user that imported the project
Summary
We recently imported dozens of projects from a self-hosted GitLab CE to gitlab.com. We only just noticed that the user that performed the import now appears to have "opened" all of the Merge Requests. The team did not sign up for user accounts until after the import, so we suspect it's got to do with that.
This potentially represents a significant data loss for our MRs (impacting reporting, search, and notifications).
Steps to reproduce
- Have a self-hosted GitLab CE
- User "A" should open a merge request
- User "B" should export/import that project to gitlab.com
Example Project
This happens reliably across all of our projects. Here's one example (user Steve Herin did the import).
https://gitlab.com/vaeit/nextgen/context-query/merge_requests/1
What is the current bug behavior?
The user that performed the import now appears to have opened all of the MRs even if they did not actually open them in the original system.
What is the expected correct behavior?
Like commits from users without an account, it would be nice if the original user information was maintained (maybe the "User Name" <user@domain>
). If the user signed up, it would be excellent if these were updated.
Relevant logs and/or screenshots
You can see that Steve is shown to have opened the MR. His name is on the comments, although there is a note about the import and it shows the original user name). His name would also appear in the assignee field if there was an assignment before (I had several examples of these, but I "fixed" them before I took the screenshot).
I only just realized, but Steve is actually shown as opening all of the MRs.
Output of checks
This bug happens on GitLab.com