Won't Fixing issues when merging from long-running branch to long-running branch

SonarQube
1

We’re using Developer Edition Version 7.9.1 (build 27448)

When merging from a long-running branch to another long-running branch, is there a way to avoid having to re-mark issues as Won’t Fix or False Positive?

We have our master branch, then a branch off of that that matches our long-running branch pattern. If we mark something in the long-running branch as Won’t Fix or False Positive and then merge it into the master branch, the master branch does not have it marked appropriately.

3

Hello Jeremy,

I assume you are not using pull requests to push your changes to the master branch.
Without using pull requests, in the current state, there’s no way to avoid marking again the issues as Won’t Fix or False Positive. Issues live independently in the long-living branches so that, for example, you can choose to mark an issue as Won’t fix in a maintenance branch but not in the master.

We are working on simplifying the way SonarQube handles branches, and your point is something we’d like to improve in the future.

4

Christophe,
We are using pull requests to get the changes to the master branch. Any help would be appreciated.

Thank you
Jeremy

6

The status of the issues are not copied from one long-running branch to another long-running branch.

If you analyse the pull request that is targeting master and mark something there, then those changes should be carried into master.