Previously it was possible to manually set the ‘severity’ of rules and filter on this ‘severity’
Currently the ‘severity’ is locked, determined by SonarQube rulings.
We would like another property, for instance ‘priority’ which the user can set themselves for each rule.
It should then also be possible to filter on this property, just like on ‘severity’, ‘tag’ and so on.
We use the following versions:
Hello Berrie,
Can you share more on how you intend to use this proposed ‘priority’ feature? Do you want to use it for prioritizing issues on overall code or new code? What determines your real-world priorities?
We want to use it to determine a standard set of actions what to do with issues of a specific priority, similar to severity. Since we cannot control severity we want a property of rules/issues that we can set.
For instance a tag that means you always have to fix it, in old and new code you touch.
Or a tag that means only use this in a specific case otherwise don’t.
Thanks for sharing.
Will the ability to tag a set of rules as ‘priority’ solve your use case? Or do you need multiple buckets/multiple priority levels/types?
Vivek,
Multiple levels would be the best, but we can make due with a prio/ no prio switch
Hi @Berrie,
I have good news about it. We are actually planning to provide, with SonarQube 10.6, a new explicit way to decide which rules should be prioritized on the overall code within a quality profile and to fail the quality gate if any related issues are found. This aims to address the main use you and many others were using the customizable severity.
Chris