We are running the python analysis, importing a PyLint report in addition to the SonarQube analysis.
The imported PyLint issues are being created with each run, SonarQube does not seem to be track already existing issues and re-creates them with each run.
See an example for the Pylint rule Unused variable in the attached image.
In addition to these duplicate warnings, resolving the code smell does not remove the existing, duplicated warnings.
Using SonarCube version 7.9.1 and SonarQube Scanner 220.127.116.113
PyLint report was generated with pylint-2.7.4 and python 3.7, running pylint --output-format=parseable.
Any help in resolving this would be greatly appreciated.