Hello,
Thanks for sharing your thoughts. I’ll set aside the broader Clean Code discussion for the dedicated thread and focus here on addressing the flexibility concerns you’ve raised.
We believe in the importance of a step-by-step approach and really appreciate your feedback every step of the way. That’s precisely why we’re introducing changes incrementally in the 10.x series.
Some of you rely on this flexibility for some use cases that currently lack alternatives. I acknowledge that deprecating and removing this flexibility all of a sudden has caused friction for some of your current workflows.
From the discussions with users, it’s clear that customizing rule severity within a Quality Profile primarily serves the purpose of prioritizing rules to improve the overall code quality. To help teams define their priorities easily and explicitly, we are working on enhancing the method for configuring these priorities within Quality Profiles and streamlining Quality Gates. However, in the upcoming version, the complete solution won’t be available just yet.
In response to your concerns, and to make the transition smoother, the next version will restore the ability to edit the old rule severity within a Quality Profile. The deprecation notice will remain in place to keep you informed about a future change.
Again, we’re working on a more comprehensive solution and, as we make progress, we’ll keep you posted with updates.
Chris