<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=571468) </details> <!--IssueSummary end--> Spike issue for researching https://gitlab.com/gitlab-org/gitlab/-/issues/534663 ### Background Two MRs were merged and reverted (under the above lined issue) in attempt to remove the default namespace and thus require the user to choose a namespace when importing from GitHub, BitBucket and Gitea. But error logs showed that some users in production were still able to request an import without selecting a namespace, despite being required to do so. ### Notes 1. The underlying table code is similar (or identical) for GH, BB, Gitea. See `app/assets/javascripts/import_entities/import_projects/components` 2. Manifest imports also use the import_projects_table.vue, so any changes will require making sure manifest import is not degraded. ## Questions 1. Should/can this be broken down into individual MRs targetting each importer? If not, is there a way to improve the code in the future so it is easier to debug ? 2. How is it possible for a user to skip selecting a target group yet be able to send the import request to the backend https://gitlab.com/gitlab-org/gitlab/-/merge_requests/193193/diffs?file=c90baa4d20e1ef90a11faf80b5f79e1e8d94ba0d#c90baa4d20e1ef90a11faf80b5f79e1e8d94ba0d_128_149 3. Were the reverted MRs the correct solution? / Is there a better solution 4. etc <!--template sourced from https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Default.md-->