SonarQube 9.9 Enterprise Edition deployed on an Azure VM.
Our Quality Gate does not allow any critical or blocker severity issues on new code but a Pull Request containing a Critical Severity issue was declared as passed. Why was this allowed through?
Apologies, I cut off the screenshot by mistake. I have updated it now.
These are conditions on New Code, which is why we are confused that the PR analysis would not fail based on this issue. There have been no changes to Quality Gates nor Profiles.
The commit the change was in was included in the PR, as evidenced by the record highlighted above.
A passing Quality Gate certainly wouldn’t be expected for 0 Critical Issues if that issue was raised in the PR (I was rather expecting it wouldn’t have been).
Are you sure the expected Quality Gate is being applied? You should see this under Project Information – it could be that the project is using another Quality Gate without this condition (like the default Sonar Way).