Dear SonarQube Community,
Our team is facing an issue with code smell detection in SonarQube.
Sometimes code smells are identified as “new” even when the files have not been modified in months or even years.
Let’s take this example:
A file called ActivityController.java has been modified on 11 DEC 2020.
In SonarQube this file contains a “new code smell” (in the last 30days). This is confusing because the has not been touched.
This behavior is not consistent: sometimes “new code smells” suddenly appear from old files and sometimes we see only the code smells we expect from new commits.
In the screenshot you can see the history of the resolution wich jumps back and forth to resolution changed to fixed and resolution removed (was fixed).
We are using Bamboo to build the code and trigger the SonarQube analysis. Shallow clones is not enabled meaning the full git history is being fetched.
- SonarQube v8.6 Developer Edition
Can someone explain this behavior? Is something wrong with our SonarQube setup or are we not understanding how this works?