Project Overview: issues severity & reliability/maintainability rating

Eva · October 2, 2024, 7:34am

Hi,

I’m confused of the current project overview statistics (overall code, C#).

The visualization of issues amount (high, medium, low severity) in combination with maintainability or reliability rating is not plausible.
Can you give me a hint how to interpret the values or which labels are relevant for the statistics? I searched for the new scale of reliability rating … but just found the matching of old & new severity (blocker & critical → high; major → medium; minor & info → low) … but is there a rating of E now possible?

The C rating of reliability with 24 medium issues is not plausible as well as the 9 high issues in category maintainability with rating A.

Thanks.
Greetings,
Eva

Installed version: SonarQube Enterprise Edition v10.6

Mikaciu · October 2, 2024, 9:55am

Hey @Eva and welcome !

You’ll find the explanation behind the metrics in the documentation:

For the maintainability rating, it’s based on time and not the number of high priority issues
For the reliability rating, if you have at least one major bug, the rating is C.

Would this answer your question ?

Eva · October 8, 2024, 9:36am

Hey,

I will add another image to point out my interpretation problem

These 2 images are screenshots from 2 different projects of 1 team.

Questions regarding maintainability:

How can a severity scale (with high, medium and low issues) map high issues to grade A? I would assume that A is no issues, B is low issues, … otherwise I would not know as a developer which issues are most important to solve …

Questions regarding reliability:

How can a project receive grade A for 6 high issues and another project gets grade C for 24 medium issues? It’s totally confusing.

Thanks,
Eva