Hi SonarCloud team,
We’re seeing a PR where the PR Summary shows a failed quality gate due to new Security Rating and Code Smells, but the PR Issues page shows 0 issues. The Issues API also returns 0 issues.
The Quality Gate API reports failed conditions, and the component-tree measures API shows that one changed file has failing new-code measures. However, we still can’t see the underlying rule/file/line issue details in the UI or Issues API.
API patterns used:
Issues API:
/api/issues/search?componentKeys=<project_key>&pullRequest=<pr_number>&resolved=false&ps=100
Quality Gate API:
/api/qualitygates/project_status?projectKey=<project_key>&pullRequest=<pr_number>
Component tree API:
/api/measures/component_tree?component=<project_key>&pullRequest=<pr_number>&metricKeys=new_security_rating,new_code_smells,new_vulnerabilities,new_violations&qualifiers=FIL&ps=500
Is this expected behavior for PR analyses, a known UI/API inconsistency, or is there another endpoint/filter we should use to see the exact rule and line causing the quality gate failure?
Thanks!