# Changing Severity is no longer possible

**URL:** <https://community.sonarsource.com/t/changing-severity-is-no-longer-possible/104354>\
**Category:** SonarQube Server / Community Build\
**Created:** [November 14, 2023, 6:50pm UTC](https://community.sonarsource.com/t/changing-severity-is-no-longer-possible/104354 "2023-11-14T18:50:56Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![aliyasrebi](https://avatars.discourse-cdn.com/v4/letter/a/9dc877/32.png) [@aliyasrebi](https://community.sonarsource.com/u/aliyasrebi)\
**Post date:** [November 14, 2023, 6:50pm UTC](https://community.sonarsource.com/t/changing-severity-is-no-longer-possible/104354/1 "2023-11-14T18:50:56Z")

</div>

hi  
Previously, when we had 9.9 community edition, we created a clone of the Sonar’s Default Quality Profile for C# code, in which we changed some of the Blockers or Critical severities. Now after the upgrade and license change (from community to developer) I no longer have that option. Sonar’s document says it is not possible to change it anymore. However, we still need it, has there been any solutions recommended by your team to get around this issue? we want to analyze our code based on Sonar’s default and also our cloned version where the severities are modified by us.

Our new Developer Edition is SonarQube version 10.2.1

thanks  
Ali Yasrebi

---

<div class="post-metadata">

**Author:** ![Chris](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/chris/32/71589_2.png) [@Chris](https://community.sonarsource.com/u/Chris)\
**Post date:** [November 16, 2023, 7:49am UTC](https://community.sonarsource.com/t/changing-severity-is-no-longer-possible/104354/4 "2023-11-16T07:49:29Z")

</div>

Hi @aliyasrebi,

We’ve restored this capability in [SonarQube 10.3](https://community.sonarsource.com/t/sonarqube-10-3-released/104484) which has just been released.

Would you mind sharing more about your case? Why do you feel the need to change some of the rule severities?

Chris