Hi,
Thanks for providing detailed explanations about your use case, @lg2de,
Regarding customizing the severity, SonarQube 10.3 is now available which restores this capability. We realized that you were using it, that we broke it for you, and we acted on your feedback.
This means that the reversal will be temporary and the severity edit will vanish in the future for sure ?
We plan to remove it only after we come up with a better solution that will answer your use cases.
More generally, we understand that customizable severity is used to enforce priorities on overall code, and for other diverse use cases we’re still hearing from. However, this flexibility was not explicitly built for that purpose. We believe that customizing the severity blurs the line between organizational policy and code quality assessment.
Of course, you should own your code policy and have the autonomy to define it as you like: you know what you need better than anyone else. That’s why we aim to develop a dedicated solution for setting and enforcing your policy on the codebase.
Chris