Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


To activate this service, pick the desired period in the drop down list Time changes... drop down list:

When a period is selected, the differential values will appear next to the project measures:


To determine the creation date of an issue, during each analysis, the following algorithm is executed to determine if an issue is new or existed previously. For each issue, if there was an issuethree of four criteria (rule; line number; line content or "hash"; and message) must match for a detected issue to be matched up with an existing one:

  • on the same rule, with the same line number and with the same hash (but not necessarily with the same message) > MATCH
  • on the same rule, with the same message and with the same hash (but not necessarily with the same line) > MATCH
  • on the same rule, with the same message and with the same line number (but not necessarily with the same hash) > MATCH


titleI am not getting the expected new issues in the Issues drilldown service when a differential view is selected?

Three reasons can explain this:

  1. 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).
  2. The algorithm detecting new issues is very good but still perfectible. Therefore new issues can sometimes appear only because SonarQubedid SonarQube did not recognize it already existed.
  3. You are looking at a period of X days which goes beyond the first analysis made after migration to version 2.5. In this case there can be a discrepancy due to the fact that prior to 2.5, data to build this service were not collected. This issue will disappear as soon as period does not go beyond first analysis.