Issue type of custom rule in IDE does not match the type of the rule template in SonarQube

SonarQube for IDE Eclipse
1
  • Operating system: Windows 10
  • IDE name and version: Eclipse 2024-12
  • SonarQube for Eclipse plugin version: 11.2.0.82640
  • Programming language you’re coding in: Java
  • Is connected mode used: Yes
    • SonarQube Community Build v9.9.8 (build 100196)

I have configured custom rules in our SonarQube instance based on a template rule.
E.g. this one based on the template “Track uses of disallowed constructors”:

SonarQubeRuleTemplate
SonarQubeRuleTemplate1019×211 13.2 KB

The template itself uses the issue type “Code Smell” by default, but in the derived rule I changed that to “Vulnerability”. In SonarQube itself, any findings for these rules properly show up as “Vulnerability”.

But when I see issues for these custom rules in Eclipse, they show up as “Code Smell”:

SonarLintRuleDescription
SonarLintRuleDescription1434×198 18.9 KB

It seems like the issue type is not properly transmitted from the custom rule in connected mode.

6

Hello :waving_hand: thanks for reporting this!

This should definitely be fixed, probably in the next release of the extension.

7

Hi @CrushaKRool,

the fix was released with 11.4.0.82756.

Best,
Tobias

1 Like
9

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.