Sonar cloud Severity New mapping does not apply why?

SonarQube Cloud
1

Hi,

If my understanding is wrong, please correct me I have seen the latest issue documentation showing the old severities are deleted and new mapping added, but still it is not showing old severities in my sonar cloud. please explain

severities mapping

image
image994×362 26.8 KB

issue:

MicrosoftTeams-image (7)
MicrosoftTeams-image (7)1112×58 7.31 KB

I saw Low mapped to MINOR and INFO but i can see in my sonar issue low mapped to MAJOR

Please suggest.

Thanks,

2

Hey there.

What specific rule is being flagged here?

3

image
image1399×164 23.2 KB

4

Thanks. Looking at this rule, it looks like this is a new rule that was introduced after we started to migrate from the old taxonomy to the new taxonomy. I’m not sure if we intend to have a strict mapping, or if this what’s documented was a general guideline when we made the move. I’ll need to wait for the person in charge of that to come back from holiday, so stay tuned. :slight_smile:

5

Hi @nagarjuna183,

You can see the impact on Maintainability is shown in blue with the same icon as the Low on the filters on the left.

However, it looks like the rule might have a custom severity in your Quality Profile, it could have been manually set to Major. Could you confirm this is the case?

6

I think no, which is my default Could you please verify that I have entered the issue code, S6754?

image
image989×389 38.8 KB