Hello Sonar Community,
We have a question regarding the handling of repeated Security Hotspots and Security Issues in SonarQube.
We have noticed that the same rules keep appearing again in the code when similar changes are introduced, even though they were previously reviewed and marked as Safe or Acknowledged.
We are aware that rules can be disabled via a custom Quality Profile, but this is not our goal. We want to keep the rules active while avoiding the need to repeatedly mark similar findings with the same status.
Is there any way to persist the status or decision (e.g., Safe or Acknowledged) for similar findings when they appear again within the project?
Additionally, could this use case be handled using sonar.issue.ignore.multicriteria, or is that approach not suitable for Security Hotspots and similar repeated findings?
Our goal is to avoid repeated manual reviews for the same type of finding, especially when the team has already decided how to handle it or plans to address it later, so it does not continuously block PR merges.
Is this behavior supported, or is there any recommended workaround?
Regards,
Eman
