We have many strict rules for our code analysis such as requiring minimum code coverage, and of course all the default critical and blockers from Sonar Way.
One problem we have is that if there is an urgent PR for a temporary fix then our merges are blocked by one or more issues. This is even more of a problem is we refactor a method name for example as it could touch dozen of files and the code coverage requirement could be flagged on them.
Today the only option for us to let the PR go through is to silence these blocking issues, and they get marked as either false positive or as minor. This mean that they are now out of focus forever.
A much better approach for long term management of the issues would be to allow the issue to be acknowledged but allowed/silenced for the current PR. This would allow for the issues to remain in the critical list of issues that should be addressed so that they can be properly fixed at a later date.
We still want to have these issues blocking a PR at least initially to force developers to review them.