Hey there.
Thanks for the feedback. It’s essential in our quest to ensure developers not only find value in our products but also enjoy and feel empowered by the experience.
If you disagree with a rule implementation, I encourage you to post the details in the category titled Report a False-Positive/False-Negative, for which we have a post detailing what is required to report (code sample, product versions, rule IDs…). Our teams are very reactive and enjoy engaging in these discussions.
There is an Administer Issue permission that in most organizations would be granted to Team leaders or experienced developers (like yourself) to be able to mark issues as False-Positive/Won’t Fix.
Somebody else (like your superior) has at least two options (maybe more) to discover these exceptions:
- Using the Issues tab of a project (or the SonarQube instance overall) to filter for issues that are marked as False-Positive / Won’t Fix if they want to do some kind of global review.
- Configure a project-level e-mail notification for Issues resolved as false positive or won’t fix
And, to be honest, Chris, if you have a superior that trusts in Sonar 100% and trusts you and your fellow developers very little (unwilling to delegate permissions, decision making)… I think that’s the root of your problem and not one that can be fixed with product changes. We create a new user role? Enable some kind of consensus-driven issue status? Your superior could just decide not to grant it.
Happy to continue discussing this.