Within SonarCloud we have a portfolio - that was created quite a long time ago - with custom dashboards, the metrics displayed there do not match the actual state of the underlying projects anymore.
ALM used: Azure DevOps
CI system used: Azure Pipelines
Languages of the repository: TypeScript/Python/Terraform
Steps to reproduce - N/A
Create portfolio
Add multiple projects to portfolio
Seemingly at some point the metrics got desynced, it seems to be isolated to one portfolio thus far
Potential workaround
Go through projects manually
Within the dashboard we have a card to display certain types of issues, here the amount of issues listed is “25”.
After clicking on the “25” issues, you get a breakdown of the affected projects, where only 2 issues show up. I have confirmed access to the other projects. As mentioned for other portfolios this still works as expected thus far.
(I changed the project name within this screenshot)
Hey @shfunke, I’m wondering if this could be a regression of the same problem you experienced a while ago. Does this project use a regex to select projects? Could you try the same trick (removing and restoring the regex)?
Okay, in that case I’m going to flag this for the devs so they can check if anything looks strange in the backend. They’ll probably ask you for the portfolio name via private message (if you could share it publicly it would save an interaction, but it’s not necessary ).
We’ve diagnosed the likely root cause of this issue: removing a project from a portfolio did not remove its issue counts from that portfolio’s dashboard; this means users would be dealing with “ghost” issues from projects that were no longer present.
The fix has been deployed as of last night, and I’ve been able to confirm in our local repro of the problem.
@shfunke Can you confirm resolution on your end? The total count and sum of the breakdown counts should now match exactly.
).