Hi @KevG,
Thank you for this suggestion! This makes a lot of sense, especially for organizations managing hundreds of repositories where scrolling to find “gaps” in coverage becomes a manual chore.
I’ve captured this feature request for our team. Improving the visibility of “un-analyzed” code is a high priority as we look to help larger teams scale their SonarQube usage more efficiently.
We’ll keep this in mind for future updates to the project import flow.
Best,
Simone