Pull Request Analysis ignores new issues in changed source file outside the changed lines of code

Hi,
Thanks - the information about the 2 strategies in the previous post was helpful.
It seem that observed behaviour results from strategy 2.

I was able to solve the problem by renaming the master branch of the project to “develop” (which is the real name of the branch). See How to change the main branch in SonarQube? for instructions.

Now the analysis spots the indirectly caused issue. This would indicate that strategy 1 was used.

BTW, I don’t think always using strategy 2 is a good idea. This would let through many issues. Therefore, it would not be a reliable Quality Gate.

Many thanks
Ulf