Why SonarQube Quality Gate passed despite having more issues?

Question

Am analysing two projects in SonarQube. I am using SonarQube Community Edition with Jenkins pipelines for two projects, and I’ve encountered an issue regarding the quality gate status. Here’s a summary of the issue counts for each project:

Project A:

• Bugs: 83
• Vulnerabilities: 3
• Security Hotspots: 9
• Code Smells: 2.6k

Project B:

• Bugs: 4
• Vulnerabilities: 0
• Security Hotspots: 1
• Code Smells: 2.6k

Despite Project A having significantly more issues than Project B, its quality gate is passing, while Project B’s quality gate is failing. I expected Project A to have a failed status based on the higher number of issues, but this doesn’t seem to be the case.

Both projects are using different quality gates and quality profiles. Could this be the reason for the difference in the quality gate status?

Additionally, is it possible to adjust the quality gate or quality profile for our own needs as a customised conditions which will enable the quality gate to pass despite having more issue count in it.