Filter out issues raised by external tools such as ESLint

SonarQube Server / Community Build Product Manager for a Day
1

Must-share information (formatted with Markdown):

  • which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
    Enterprise Edition Version 8.9.9 (build 56886)
  • what are you trying to achieve
    I want to filter out issues raised by external tools such as ESLint and only see issues raised by. Sonarqube
  • what have you tried so far to achieve this
    Go to the issues page but there is no filter to see issues only raised by Sonarqube
2

Hi,

To be clear, you still want these issues to be raised, you just want to be able to filter them out of the Issues page?

 
Ann

3

Yes, that is correct.

4

Hi,

Sorry, but as you’ve observed, that’s just not possible. Could you explain your use case a little further (so I can maybe interest the Product Managers)?

 
Ann

5

We want to allow teams to integrate external tools they already use such as ESLint, Bandit, GoSec, etc. into their sonarqube projects. We also want the ability to filter out issues raised by these external tools and only have a view of sonarqube issues.

When someone (e.g management) looks at issues for a particular project which incorporates issues raised by a tool like ESLINT, they might see that the project has thousands of bugs only to realize that 90% of these bugs have been raised by ESLINT (e.g the screenshot below). There is no way to distinguish if an issue is raised by sonarqube or not unless one manually goes through the issues list of a project one by one and look for the external tool’s tag (e.g ESLINT).

Therefore, It would be nice if:

  1. There was a way to filter out issues raised by external tools on the sonarqube issues page
  2. Enable/disable if the numbers from issues raised by external tools should show up in the sonarqube dashboard for the projects.

image
image976×90 13.3 KB

6

Hi,

Thanks for getting back to me.

This seems like a sound onboarding strategy. As a followup, do you intend to transition teams off of those tools, making this a transitory problem? Or is this a long-term issue?

 
Ann

P.S. I’m going to move this to the Product Manager for a Day category.

7

This is a long-term issue.

1 Like