Consider supporting the aggregated VSA in user namespaces
Currently, licensed group-level and project-level VSA requires that the top-level namespace is a Group. Would it make sense to support personal namespaces?
Research:
- How many personal namespaces are there? How many of them are licensed?
- Project, issue, MR count in personal namespaces.
- Decide whether its worth the effort to extend VSA to work with personal namespaces.
Context:
A wrong assumption in the license check recently an issue (due to a bug) where the VSA backround worker got stuck: !115484 (merged)