# Post Upgrade to SonarQube 8.9 LTS upgraded rules are showing up in a Different category

**URL:** <https://community.sonarsource.com/t/post-upgrade-to-sonarqube-8-9-lts-upgraded-rules-are-showing-up-in-a-different-category/58872>\
**Category:** SonarQube Server / Community Build\
**Created:** [February 23, 2022, 4:51pm UTC](https://community.sonarsource.com/t/post-upgrade-to-sonarqube-8-9-lts-upgraded-rules-are-showing-up-in-a-different-category/58872 "2022-02-23T16:51:07Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![shoaib5035797](https://avatars.discourse-cdn.com/v4/letter/s/3e96dc/32.png) [@shoaib5035797](https://community.sonarsource.com/u/shoaib5035797)\
**Post date:** [February 23, 2022, 4:51pm UTC](https://community.sonarsource.com/t/post-upgrade-to-sonarqube-8-9-lts-upgraded-rules-are-showing-up-in-a-different-category/58872/1 "2022-02-23T16:51:07Z")

</div>

- versions used (SonarQube, Scanner, Plugin, and any relevant extension) - 8.9 LTS
- error observed (wrap logs/code around triple quote ``` for proper formatting) - Post Upgrade some of the rules which were under vulnerabilities and now code bug still show under vulnerabilities. The rules updated in SonarQube upgrade did not carry through for vulnerability findings. Vulnerability findings that should be Code Smells are still Vulnerabilities even though clicking on the rule will show a Code Smell.

---

<div class="post-metadata">

**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\
**Post date:** [February 23, 2022, 7:36pm UTC](https://community.sonarsource.com/t/post-upgrade-to-sonarqube-8-9-lts-upgraded-rules-are-showing-up-in-a-different-category/58872/2 "2022-02-23T19:36:51Z")

</div>

Hi,

Welcome to the community!

When we re-examine a rule and update its type, existing issues raised by that rule are not also updated. This was a conscious choice on our part, and an attempt to minimize disruptions to our users.

If you like, you should be able to Bulk Change those issues to match the current rule type.

&nbsp;  
HTH,  
Ann

---

<div class="post-metadata">

**Author:** ![shoaib5035797](https://avatars.discourse-cdn.com/v4/letter/s/3e96dc/32.png) [@shoaib5035797](https://community.sonarsource.com/u/shoaib5035797)\
**Post date:** [February 24, 2022, 2:45am UTC](https://community.sonarsource.com/t/post-upgrade-to-sonarqube-8-9-lts-upgraded-rules-are-showing-up-in-a-different-category/58872/3 "2022-02-24T02:45:47Z")

</div>

Thank you Ann ! It’s helpful