In order to deactivate a rule, you need to create a custom Quality Profile where the rule is NOT activated. Then you need to associate this new Quality Profile to your project.
That said, can you share some details about your project such as the logs of the analysis and the number of JS LOCs? Having to wait 40min is indeed not the kind of performance we expect on JS projects with SQ 8.9 LTS. The expectation is to be able to process 950+ LOCs per second for a project made of mainly JS code.
what I mean is that sonar properties are not take into account in latest LTS. And my company informed that is following the best practices, which you recommend LTS version (maybe we are wrong?). So it’s confusing regarding your policy, that version LTS is recommended, but bugs are not ported to latest LTS, then for what LTS version is used for?
This property is there to control which issues you don’t want to see or not in the UI. The property has no impact on the fact the rules are running or not in the analyzer part. It’s probably misleading I admit it.
We do consider “Speed” as a feature and so any change we do to improve the speed of the analysis is done in the latest version. You should accept to use the latest version of SonarQube if you want the fastest analyzers.