Old issue types, custom severities undeprecated in 10.8

[ganncamp (G Ann Campbell)]

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.

[anon40266202]

Hi Ann,

if i understand this correctly

Adding two more levels of severity to SonarCloud

We wanted to add some additional information on what this means for the APIs. When querying rules or issues, you may start to see INFO and BLOCKER appearing as statuses at the quality level (i.e. a rule might have a reliability severity of BLOCKER). It is also possible to create rules/issues with these additional severities. These APIs in particular are affected: api/issues/* api/rules/* api/projects/export_findings api/qualityprofiles/compare api/qualityprofiles/changelog This is the case fo…

this means there will be 5 severities =
Blocker, High, Medium, Low, Info

alternatively to the current
High, Medium, Low

replacing the former
Critical, Blocker, Major, Minor, Info

in the future starting with Sonarqube 10.8 ?

Gilbert

[ganncamp (G Ann Campbell)]

Hi Gilbert,

Both the old and the new workflows will be available:

Bugs, Vulerabilities & Code Smells with Blocker, Critical, Major, Minor, Info

and

Consistency, Intentionality, Adaptability, Responsibility with Bocker, High, Medium, Low, Info.

 
HTH,
Ann

[anon40266202]

Hi Ann,

those news made my day

Gilbert

[Wiebke (Wiebke Schwierz)]

Hi Ann,

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.

Regards,
Wiebke

[john.clifton]

Hi,

Yes, you will continue to be able to set a quality gate to confirm you have no issues of a particular severity.

[vka]

Hi John,
Any ETA for 10.8 ?

[john.clifton]

We are aiming to have 10.8 out this quarter.

[andi (Andreas)]

Hi,

will this also fix the java exception that is thrown from sonar-scanner, when the generic issues file contains a severity for an issue?

[ganncamp (G Ann Campbell)]

Hi @andi,

Could you create a new thread for that with all the details?

 
Thx,
Ann

[Colin]

In addition to this update, those interested can read this update from Sonar’s Head of Product Management.

Our commitment to you – and an update on severity ratings for software quality

Yesterday, we shared more information on restoring the ability to customize rule severities in SonarQube Server 10.8 – see our blog here for all the details (also copied below). The blog also includes four engineering principles that will further guide our product delivery and development. Our commitment to you – and an update on severity ratings for software quality The speed of software development and product delivery is increasing for organizations everywhere – including here at Sonar. Just…

[zorro]

Great News, I wish if you bring the same theme option as 9.9 in next LTS version.