The next step would be to manage your technical debt on your current developments in order to keep it under control.
To deal with that, Sonar offers you the a Differential Services feature is provided on measures, issues and coverage by unit tests on new code.
To determine the creation date of an issue, during each Sonar analysis, Sonar executes the following algorithm : for is executed. For each issue, if there was an issue:
|title||I am not getting the expected new issues in the Issues drilldown service when a differential view is selected?|
Three reasons can explain this:
- This Issues Drilldown service only shows added issues, not fixed ones. Therefore the number you see in this service can be different from the one displayed on a dashboard through the Rules Compliance widget (that displays added issues - fixed issues).
- The algorithm detecting new issues is very good but still perfectible. Therefore new issues can sometimes appear only because Sonar SonarQubeTM did not recognize it already existed.
- You are looking at a period of X days which goes beyond the first analysis made after migration to Sonar version 2.5. In this case there can be a discrepancy due to the fact that prior to 2.5, Sonar was not collecting the info necessary data to build this service were not collected. This issue will disappear as soon as period does not go beyond first analysis.
A live example is available on Nemo: Sonar (from Git).