Portfolio: issue after changing project's branch

[ftlvz]

Hi,

I’m using SonarQube Cloud Enterprise and I have a Portfolio whose definition used component project’s’ main branches.

I updated the portfolio definition to use a branch with a specific name. This branch exists in all compoenents, but for some of them it’s NOT the main branch.

After this update, if I go to “Portfolio Breakdown“ page, I cannot see anymore the Releasability, Security, Reliability, Maintainability, Security Review and LOC for components where the selected branch is NOT the main branch, even though the branch has been analyzed (as reported in the Measures page of the Portfolio itself).

Is this a known issue or am I doing something wrong?

Thanks

[alexis.escarcega (Alex Escarcega)]

Hi ftlvz,

Thanks for bringing this up to our attention.
Also thank you for providing helpful details to reproduce this issue.
I have created an internal ticket to track its fix.

Thanks,
Alex