I’m interested to understand why you need these ratings at the Application level. They don’t impact the Quality Gate since that’s calculated from the underlying projects. What do you plan to use the information for?
The obvious answer is just that the entire SonarWay recommends focusing on new code and not being overly concerned with the past. So why provide this capability on overall code but not new code?
But anyway, here’s a specific use case… I have applications comprised of 100+ projects. Let’s say 50 of the projects are failing their respective quality gates. I now have a long banner down the left showing all the various project’s new code quality gate failures across all the different static analysis categories. Somewhere mixed in there are reliability quality gate failures with B’s, C’s, D’s, and E’s. How do I quickly learn what my new code reliability rating is? I guess I need to scroll down and take notes on each project that is failing to determine what the worst rating is for reliability. Rinse and repeat for the other categories. That letter grade should be right there on the overview.
Next, clicking on a letter grade on new code should take me directly to the measures tab with that static analysis grade for that category selected, summarizing for me all the projects that have contributed to this failing letter grade (as is the case for overall code overview tab).
Which brings me to the crux of what the I think the bug is… If you look at measures, there is a letter grade for new code Security Review, but nothing else. That inconsistency seems like a bug to me, preferably with the fix being for all categories to show the letter grade on the measures tab for new code. Do you agree? If you agree that’s a bug, fixing it certainly at least gives me a way to do what I suggest above, but additionally once it is fixed for the measures tab, why not show it on the new code overview, if for no other reason than consistency in the UI.