Hi,
I am using a SonarQube Server with Developer license, version v2025.1 (102418), no plugins or extension. SonarQube is running on a Windows Server 2022.
We were looking at a specific date range and tried to understand which issues came in between the two dates. We see in the activity overview issue count which doesn’t match with the issue overview count.
28 Feb - Issues: 38,314
27 Feb - Issues: 38,172
When I go to the issue overview and filter for the “Creation Date” to 27 Feb and 28 Feb, it only shows 38 issues. I am expecting 142. Why is a gap there? I checked that there are no other filters active in the overview. We are looking at all code and not only new code.
We often use the activity overview for progress tracking, but we unsure now if the metric is correct.
While we do record in the database the timestamp of issue creation, what we expose through the UI is the issue backdate.
Further, in the long term you’re going to have a hard time tracking the issues that were added at any given period in the past. That’s because when issues are fixed in code they’re marked Fixed in SonarQube, and then eventually cleaned out of the database.
Thanks for the quick response. I understand now why the metrics can differ. Is there a way to see / to filter which issues came in / were recognized on a specific date (not created date)?
There is, but it’s not pretty. Creation date is part of the api/issues/search response, so you could make a direct API call and filter that data manually.
Hi,
I’ve tried something like this:
“api/issues/search?projects=Database&createdAfter=2025-02-27T00:00:00%2B0100&createdBefore=2025-02-28T23:59:59%2B0100&s=CREATION_DATE&resolved=false”
The result is matching with the filter creation date in the UI. The question is, which parameter can I use to filter the issue for, before the back dating is happening. The creation date parameter is after the back dating.
I’ve provide some screenshot from the analysis. The backdating wouldn’t explain the jumping and falling of the issues, since we didn’t have any rule changes, sonarqube updates or excluded files which are included now. We just use the standard analyzer and no addons or plugins. The chart suggest the rise and fall of over 1k issues. In the overview one can only see about 500 (open+fixed). I can’t explain the numbers in the activity overview with the back dating. Is there maybe another explaination or is the activity overview not functional right now?
I’ve just taken another look at the API docs. When I checked them originally, I saw there were two dates in the response but I didn’t look closely enough. I’ve just noticed that one of them is creationDate and the other is `‘updateDate’, rather than the backdated issue date, as I had assumed.
So unfortunately, you’re not going to be able to track this down exactly.
There can be many reasons for this. Based on your graph, it looks like your issue count dropped to ~0 a couple times. At a guess, the analysis configuration was (briefly!) edited incorrectly, so that none of the issues were detected. This could be caused by a change in sonar.sources or changes to inclusions, exclusions, or even the job checkout.
I was not wondering about the drop to 0 or jump. This was clearly caused by profile switching. I mean the up and down March. Another example for the strange behavior fr the activity graph is when I am looking for all issues till Mar 8, the number should match with the number of the overview:
In the Issues tab, you’re always going to see the current state. Even if you filter by creation date, you’ll only see the issues from that date that are still open.
