Manifest import: misleading path in status table when user cannot create top level groups
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
A customer reported an issue they experienced with manifest import. On the status page, the target group was showing the importing user's personal namespace, rather than the group selected from the dropdown.
We found that Import::ManifestProviderRepoEntity checks the user's top-level group creation permission when generating the API response for the import status page.
This doesn't appear to affect the actual import, as the project is still created in the chosen target, not the user's personal namespace.
If this is purely a bug in the API response, the solution may be as straightforward as removing the permission check in Import::ManifestProviderRepoEntity and trusting that permission to import into that group was confirmed elsewhere.