SonarQube 7.9.1 LTS Enterprise
Scenario - There is a COBOL file with several issues identified by SonarQube. At a later date some code changes are made, which leads to a parse error during sonar scanner execution. Now, because of parse error ALL open issues in the COBOL file gets closed automatically. I am not sure if this is how it should work. I would expect SonarQube to just exclude the file from analysis when it finds a parse error (assuming the file did not change).
Problem with current implementation is that when parse error gets fixed in code, SonarQube treats all “existing” issues as “New” and this fails the existing debt logic.
Can this be handled within SonarQube such that parse errors do not close the existing issues ?