404 when importing a personal project

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Summary

When attempting to import a GitLab export file into GitLab.com as a personal project, and the current user has a Highest Role of Developer across all groups they are a member of, the user sees a 404 error. When this happens, it isn't clear why, so the user doesn't know what to do.

Steps to reproduce

1. Export a GitLab project.
2. Log in to OR ensure the GitLab user account you are logged in to:
   • is a member of at least one group and
   • their Highest role across all groups is Developer and
   • they have Developer role in only one group
   • the group where they have Developer role does not have any subgroups
   • in other words, the dropdown in https://gitlab.com/projects/new#blank_project should fetch only one group where the user has Developer role
3. Goto /projects/new.
4. Click on GitLab export OR any.

Example Project

An example user account is needed, not an example project 😄

What is the current bug behavior?

• The user sees a 404 when attempting to upload their export with the URL (https://gitlab.com/import/gitlab_project/new?namespace_id=<GROUP_ID>&name=&path=) using a namespace_id where they have Developer role.

What is the expected correct behavior?

• The user should be able to import a personal project regardless of their roles in GitLab groups

Possible fixes

I believe that the roles required to Create and Import projects might be clashing.

• Create requires Developer and above
• Import requires Maintainer and above

Workaround

• The user can create a group OR
• The user's role can be upgraded to Maintainer instead of Developer OR
• The user can be given Developer role in more than one group/subgroup

NOTE: Updating a user's role in a project does not work.