Spike: Remove default selection for target namespace in third-party import tables

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

• Close this issue

Spike issue for researching #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 !193193 (diffs)
3. Were the reverted MRs the correct solution? / Is there a better solution
4. etc