SonarQube not detecting removed issues

Question

In the documentation of the SonarQube issue lifecycle (https://docs.sonarqube.org/display/SONAR/Issue+Lifecycle) one of the two possible resolutions is:

• Removed - set automatically when either the related coding rule or the file is no longer available. The rule may not be available either because it has been removed from the profile or because the underlying plugin has been uninstalled. The file could be unavailable because it has been removed from the project, moved to a different location or renamed.

Even after analyzing dozens of commits of an open-source project, in which files were clearly renamed and moved, the Removed count is still zero.

Does anybody understand why this is? Shouldn't the counter increase?

Answer 1

SonarQube detects file move, so when E.G. A.java is moved to B.java, its issues will move with it.

Removed, as described in the docs, is used when the rule no longer applies. Try removing a high issue count rule from your profile and reanalyzing; you should see the Removed number increase.