Measures section doesn't reflect SonarCloud rules mode (MQR)

Hi all!

I have just found that the “Measures” section doesn’t reflect the rules mode in SonarCloud and the values are wrong (still using old model)

The section is supposed to allow the user to review Reliability, Security, Maintainability and check values for measures in new code and overall code, but this section is still showing “bugs”, “vulnerabilities” and “code smells”.

And that means that the values for open issues in any other section is different.

This is show in main summary view of a project:

And then if you browse to measures section you will see that reliability has 23 bugs (and not 25):

That’s because this section is still using old metrics (bugs) for reliability instead of using new metric (reliability_issues).

I don’t know if this is a bug or a feature because reality is that it is true that there are 23 bugs, and it is also true that there are 25 open issues (23 bugs and 2 code smells) for reliability domain.

The only thing I can say is that this is incoherent and the user expects to see “open issues” in Reliability section inside Measures.

It seems that someone forgot to refactor this page when the mode was changed to MQR in cloud.

You can browse this project to see what I’m trying to explain:

Could you please check this out and fix it? We don’t want to see issue types anymore in measures page, we just want to talk about issues, and the software quality impacted.

Thank you and best regards!

Hi @acalero ,

Thank you for your post. Yes, we’re indeed aware of this discrepancy. SonarQube Cloud is still in a hybrid mode, where it shows what we call “Standard” data (Bugs, Code Smells, etc) in some places, and MQR (“Multi-Quality Rule”) data (Reliability issues, Maintainability issues, etc) in others.

There is a plan to clean this up and move the entire platform to the MQR experience (this is already the case on SonarQube Server, which now only shows MQR data by default). In the meantime, apologies for the confusing experience and the discrepancies in certain places.

Thank you @Wouter_Admiraal for the information!

Is there any estimated time of arrival for this?

Best regards.

I sure hope we’ll work on it this Summer :grin: . But right now, there’s no definitive timeline.