We have used sonarqube for quite a while. We migrated from LTA 9.9 version to 10.6 and now are on 10.7. We noticed a few things where we need your help:
We had some conditions defined in the Quality gate: i.e No Blocker/Critical issues. The severity levels have changed now to High Medium Low. But when we go to define a condition based on the new severity definitions, we don’t see those options. The older options of Blocker/Critical still exist. We don’t see High. In many places in your documentation too, we see references to Blocker/Critical
I understand that with the CleanAsYouCode approach, the prescribed way is to have 0 issues in new code. But for legacy code, we may want to specify conditions like the one above for old code. How can i do it with 10.7?
In SonarQube v10.8, we will be bringing back the “standard” experience (what you had in SonarQube v9.9) and giving you the option to switch between that and the new experience. We’ll also be making some changes to the new experience (5 severities instead of 3). You can read more about that here: Old issue types, custom severities undeprecated in 10.8
SonarQube v10.8 will also let you set a QG condition on High Severity issues
For now, it probably makes sense to keep your QG condition of Blocker Issues. When SonarQube v10.8 comes out, you can decide which experience you want to use, and you can set conditions that match the new severities if you choose. The condition on Blocker issues works the same in v10.7 as it did in v9.9.