How to know the impact before enabling rule

Must-share information (formatted with Markdown):

  • which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension) - Community Edition Version 8.0
  • what are you trying to achieve
    Before enabling any given rule (mandatory or optional), can we get some metrics on the impact? Team/projects affected, etc.
  • what have you tried so far to achieve this
    Doing POC on how to implement this .

When enabling new rules, new issues raised by those rules will be backdated assuming that SCM information is available (basically, git blame information) to the date that line was last changed.

With a Quality Gate focusing on New Code (following the Clean as you Code approach) the impact should be minimal.

@Colin_SonarSource Thank you for your response . But is there any way I can see the projects that will get impacted when I enable a rule . (Like enabling a rule will impact 50 micro service ) this comes as a chart or list .

No, sorry. There’s no way to know if a rule will raise issues on a project before the project is rescanned other than trying to scan those projects with an updated Quality Profile on a non-production instance of SonarQube, or as a new project with a different project key.