Dear Team,
On the latest 10.1 Community version, we are not able to view previous analysis result and espacially details when it comes to failure when using the previous version based for new code. This is very frustrating to have a failure on the report to check what’s wrong and have on the dashboard only the latest version visible
Is it normal ? How to adjust it?
Thank you in advance for your help.
Benjamin
Hi Benjamin,
Welcome to the community!
Could you share a screenshot of where you’re looking for this, please?
Thx,
Ann
Hello Ann,
I’m checking this in the Activity. If I want to get details on this specific version at the time, what was the bugs and issue, I can’t. How can I check this ?
Thank you in advance for your help.
Best regards,
Benjamin
Hi Benjamin,
Thanks for the screenshot and the explanation. They provided the context I need.
And unfortunately, you’re not going to be able to pull the data you’re looking for out of SonarQube.
What you can get: aggregate issue counts by type or severity.
What you can’t get: a list of issues raised in a particular analysis. Why not? Because the issues in SonarQube reflect what was found in the last analysis. Let’s say an issue was present in the June 16th (from your screenshot) analysis, but then fixed the next morning and Closed in the following analysis. It’s still reflected in the historical issue counts that were recorded on the 16th, but it got cleaned out of the database 30 days after it was marked Closed on the 17th. So you’re not going to find it in any list of issues today.
Does that make sense?
Ann
Hello Ann,
Can this be a feature? Because having the latest report is not that relevant at the end. If on the v1 we have huge amount of bug and vulnerability but on the v1.1, the new code is fine, we wouldn’t know what was on the list on the new code to fix them.
Thank you in advance for your help.
Best regards,
Benjamin
Hi Benjamin,
I don’t understand. Until old issues are fixed in code, they’re still findable in SonarQube. The point I was making is that you can’t get a reliable list of all the issues that were new on X date, or present in the code on X date.
Ann
