Project Import Failing when Private visibility level disabled
Summary
As described by customer:
Our self-hosted GitLab instance currently restricts the Private and Public access levels; only Internal is allowed. We are using the GitLab import from GitLab export feature. I have a regular (non-admin) user who is unable to import a previously exported project - they get an error banner with: "Project could not be imported: Visibility level private has been restricted by your GitLab administrator".
I am able to use the same export file and import it successfully. The strange thing is that the visibility level of the imported project is set to Private, even though the original project was Internal, and Internal is the only allowed visibility level.
Shortened summary:
Internal project is exported, but cannot be re-imported because default visibility is set to private on import, yet private projects have been restricted, thus blocking the import of the project.
Steps to reproduce
- Restrict Private and Public visibility levels restricted in
/admin/application_settings
. - Create a new Internal project, add a file through the UI, save it and use setting=>export to generate the export file.
- Take the export file and use the "import from GitLab export" option.
Example Project
What is the current bug behavior?
"Project could not be imported: Visibility level private has been restricted by your GitLab administrator".
What is the expected correct behavior?
Project should import with Internal visibility level.