Hi Ann,
thanks for your understanding for forwarding this issue. I am not the only one waiting for this feature:
https://community.sonarsource.com/t/dealing-with-false-positives-wont-fixes/35173
https://community.sonarsource.com/t/new-branch-analysis-picking-older-codes-and-issues/45761/5
https://community.sonarsource.com/t/issues-marked-as-resolved-wontfix-in-master-branch-are-still-shown-as-issues-in-other-branches/64180
I have to admit, that it is mentioned in the documentation. At Defining new code it says
Any changes made between your branch and the reference branch are considered New Code.
What confused me was Issues with
Unmatched “raw” issues are considered new
I somehow mixed up “New Code” and “New Issues” in my head. So in combination it means “show me issues, which are not found on main, on lines that are different from main”. Am I right?
Btw. on Branch analysis it says
Issues can be synchronized between branches if you’re using the Reference Branch new code definition. When using this new code definition, any new issue in the reference branch that comes from a feature branch automatically inherits its attributes (type, severity, etc.) from the feature branch. A comment is added to the change log of the issue on the branch:
The issue has been merged from '<branch-1>' into '<branch-2>.
I guess the status is none of these attributes? Maybe this could be made a bit clearer here.
I cannot see the mentioned comment at my issue in the master/main.
Thanks!
Regards,
Carsten
PS: We are working on migrating to SonarQube 9.9.