Hi Claire, just looking through the PRs, I’ve just found an example where it works, using your hint about covering some projects.
For example in this case, the repository has 12 services stored in separate sub-folders, with each service defined as a mono-repo project in SonarCloud. I can see all projects in SonarCloud and for an specific project the pull requests that include the changed services(projects). For example here are the PRs for a single service/project and the PRs that include it:
Normally we would only update a single service at a time, in this instance I can see the “build” in BitBucket for the Sonar analysis and that the pull request is registered in SonarCloud (circled red in the image above). But the widget fails to load anything and I get the “not found” error:
If I compare this to a PR that has all 12 services included (circled green above). You can see that the widget now works.
I’d expect the widget to work regardless of the number of projects included and show only those that were part of the pull request. Following a component based development model with a mono-repo, we would very rarely change multiple projects in a build, hence splitting it across multiple Sonar projects for individual analysis.
John