In SonarQube 10.2 we introduced changes to how issues are classified, including the removal of customized rule/issue severities. After discussions with you, our users, we’ve decided to change direction. Starting in 10.8, we will undeprecate the ability to customize rule severities, allowing you to continue using the concepts and workflows you are familiar with (e.g. bug, vulnerability, code smell) from earlier versions of SonarQube.
If you’ve adopted the new classifications and severities from 10.2 and later releases, they won’t be removed and you can continue using them. We will also add the ability to customize these new severities.
Both approaches for classifying issue types and assigning issue severity will be available going forward and you can determine which is more suitable for your business. Please stay tuned for more details in early December alongside the 10.8 SonarQube release.
great news
Will it also still be possible to use the old Severities like Blocker, Critical, etc in the Quality Gate? E.g. check with QG that there are no Blocker and Critical issues.