Steps to reproduce:
- Analyze (maven-based) project Foo that has sub-projects A and B
- Analyze sub-project A independently => in SonarQube, A becomes a project
- Delete project Foo
- Go on dashboard of project A and drilldown on issues: measures are correct but if you click on a file that is supposed to have issues, you won't see them
- Same if you try to search for the issues in the Issues page
Root cause: during the analysis that turned sub-project A into a project, the batch did not update the "root_component_id" of the issues (it still reference the ID of Foo).