Must-share information (formatted with Markdown ):
which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
how is SonarQube deployed: zip, Docker, Helm
what are you trying to achieve
what have you tried so far to achieve this
Sonarqube Enterprise Edition
Hello!
We just upgraded from 10.0 to 10.2, and for our surprise we noticed that the option for changing the severity of the rules in the quality profiles just disappeared
We are used to change the severity of the rules to better adapt to the code quality standards that we have
I feel that this a huge change, and unfortunately not a good one
Welcome
see this thread for all the details
Hi,
reading the forum nearly every day, i was very surprised to see that rule severity has gone with Sonarqube 10.2 after updating one of our test instances to Sonarqube 10.2 !?
Severities are all at once deprecated and the link still has 404, means i don’t know what are your intentions
https://docs.sonarsource.com/sonarqube/10.2/user-guide/rules
AFAIK the deprecated state means it will vanish during the next versions, but here it was deprecated and switched off simultaneously, means there …
TL;DR
Gilbert
Hello!
Thanks for the quick reply,
We are using a plugin that does not support above 10.2 versions of sonarqube. Will try to contact with the vendor
Apparently this functionality is also going to be removed after 10.4
According to the product owner
Hi Gilbert,
You will be able to continue relying on customized severity. We are exploring other possible solutions but are not yet ready to share more details at this time. Rest assured that we are mindful of not disrupting the existing workflows.
For updates, we’ve added a portal card to our roadmap, inviting other users to express their needs and enabling those interested to stay informed about our progress on this topic.
Regarding Clean Code in our products, I suggest continuing the discus…
But i have no further details / any news.
1 Like
Colin
November 14, 2024, 9:34am
6
Hey @mnunezdm_repsol
If you haven’t already seen, we are restoring the ability to customize severity. You can read more here:
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 …
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.
