Is there a way to control the grades in portfolio per user needs

SonarQube Server / Community Build
,
1

Hi
We are using Sonar server Enterprise Edition v2025.1.
Per this page:

“SonarQube Server converts each project’s letter rating to a number (see conversion table below), calculates an average number for the projects in the portfolio, and converts that average to a letter rating”

Now, let’s say my portfolio has 1 application with 10 projects, where 9 of them have grade A in Reliability, and 1 with grade E.
These 9 projects are old and hardly in use, while the 1 project is the most important in terms of amount of code and daily work. Per today logic, the average grade will be A.
Is there a way I can tell sonar to give more “weight” to this project compare to others? From my point of view, it’s more reasonable it will give more percentage for project per lines of code or other parameter user will choose, rather than just simple average. Does the only work around is to create separate portfolio for these projects?

I’m asking as today I’m sending daily report with the portfolio grades, and most of them with grades A. However, that’s not really reflect the real status, as most of the projects are not in use and with small amount of code (but I still want to include them), and the significant ones are with grades of C to E, but their overall number in my application is lower. So people who are getting the mails think the overall status is good and safe, where actually it’s not correct (and in addition it doesn’t give them any motivation to go check the projects with E grade).
We should have the ability to control/modify the calculation, and not just get the default of simple calculation of an average number for the projects in the portfolio.

3

Hi,

No.

Yes.

And keep in mind that you can create a hierarchy of portfolios if you really must have a portfolio that contains all of these projects together. So you could have one portfolio, let’s call it “Significant”, and another called “Archived” and roll those together in a top-level portfolio, “All”.

Although to be honest, I really don’t understand why you want to track projects that aren’t in use. Surely that’s like tracking a rock in that there’s no movement?

 
HTH,
Ann

4

I assume your hierarchy suggestion is similar to what present here, right?

1 Like
5

Hi,

Yes, exactly.

 
Ann

1 Like
6

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.