importing gitlab project to a group fails to import issues/MRs/pipelines
Summary
I'm currently migrating our team from a self-hosted gitlab-ce to gitlab.com. I first exported the top level group with all its subgroups, which worked fine. Then I tried to import the first project into one of the groups. After the import I realized that all MRs/Issues/Pipelines etc. are gone.
Then I just tried to import the project to my own account, without any group. This worked and all issues etc. have been created.
Steps to reproduce
- Export a project from a group in a GitLab installation.
- Import this project into a group on gitlab.com
What is the current bug behavior?
Merge requests, issues, pipeline runs, etc. are not been imported.
What is the expected correct behavior?
Merge requests, issues, pipeline runs, etc. should be imported.
Relevant logs and/or screenshots
Output of checks
This bug happens on GitLab.com
Results of GitLab environment info
Information of the exporting GitLab.
Expand for output related to GitLab environment info
System information System: Debian 10 Current User: git Using RVM: no Ruby Version: 2.7.2p137 Gem Version: 3.1.4 Bundler Version:2.1.4 Rake Version: 13.0.1 Redis Version: 5.0.3 Git Version: 2.29.2 Sidekiq Version:5.2.9 Go Version: go1.13.5 linux/amd64 GitLab information Version: 13.7.4 Revision: 79ee819cc84 Directory: /home/git/gitlab DB Adapter: PostgreSQL DB Version: 12.5 URL: https://git.********.com HTTP Clone URL: https://git.********.com/some-group/some-project.git SSH Clone URL: git@git.********.com:some-group/some-project.git Using LDAP: no Using Omniauth: no GitLab Shell Version: 13.14.0 Repository storage paths: - default: /home/git/repositories GitLab Shell path: /home/git/gitlab-shell Git: /usr/local/bin/git