Follow-up from "Fix GitLab Migration groups & projects visibility levels to be preserved"

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

• Close this issue

The following discussion from !109026 (merged) should be addressed:

• @rodrigo.tomonari started a discussion: (+4 comments)

  I don't understand why a project entity type would allow a blank destination_namespace 🤔

  Don't projects always need to be imported into group namespaces?

  Am I missing anything?

This issue isn't problematic, as long as only the backend creates the project migrations, because the backend sets the destination_namespace.

When we allow users to create project migration, not validating the existence of the destination namespace or allowing a blank value would cause the same issue as Import from GitHub API can ignore target_namespace (#381902 - closed), where the project would be created in the user's namespace.