We’ve now released SonarQube 10.2.1 which fixes this problem.
See more details here:
About the change made to the severity in 10.2, it was mentioned in a quite large ticket related to the new Clean Code taxonomy (SONAR-20023). To give more visibility, we’ve now created some dedicated tickets about the changes applied to the old type and severity: SONAR-20517, SONAR-20518. Thanks for the feedback.