We’re using SonarQube 8.9.8. We marked some false positive issues as resolved in our master branch (but the master branch isn’t the main branch in sonarqube). However, SonarQube still points out these issues in other branches created from master and fails the analysis.
Is there any way to mark an issue as resolved in a way so it take effect across all branches?
Even security hotspot issues that were marked as “safe” in master branch are still shown as issues in new branches.
What I am trying is similar to yours. I am seeing that if the code smell is marked as “wont fix” in the master then it gets synchronized with the new branches created off the master. But what if I want to synchronize the code marked as wont fix from a branch to the master. So that eventually the new branches created from master gets synchronize with that branch which marked the code smell as wont fix.
The transferring of issue status from one branch to another is a one time thing that happens on the first analysis of a branch. Since your master branch is already analyzed, it won’t get issue statuses from any other branch.