False-Positive doesn't retain that status after merge

SonarQube Developer Edition 9.9.2 LTS
Sonar-scanner 5.0.1.3006
Jenkins 2.440.2 LTS
SonarQube Scanner for Jenkins plugin 2.15
SonarQube deployed inside Kubernetes with Docker image

Hi Community,
We are using the SonarQube in our CI infrastructure to analyse C/C++ code.
Recently we have faced with the issue related to retaining issue resolution status after merge into master.
How the workflow looks like:

  1. During the feature branch scan, SonarQube found an issue:
    image
  2. We resolved the issue status as “False Positive”:


3. We re-run sonar scanner on the feature branch and after successful scan merged it into master
4. After merge feature branch into master sonar scanner fails with the issue that was previously resolved as " False Possitive" in the feature branch before merging:
image

For all feature branches, master branch is configured as reference branch in the project settings.
As I know from documentation, issue resolution retain its status after merge if reference branch is configured for the feature branch. Branch FAQ
Please help us to find the root of the issue.
Thank you for your advice.

Hi,

Just to dot the i’s could I also have a screenshot of that (re)open issue in the main branch?

 
Thx,
Ann

Hi @ganncamp ,
Thank you for reply. We’ve already resolved it manually as Won't Fix and for this reason I did not attach it.
Here is the resolved issue:

Hi,

Would you mind showing the issue changelog? Click on ‘6 days ago’ to see it.

 
Thx,
Ann

Screenshot 2024-04-03 at 16.12.28

As I see - the issue was created by another branch (not the same branch where we’ve resolved it),
But in this branch - all scans were passed successfully without any issues, besides I can’t find this issue neither in new code nor in old code.
Here is activity for the that branch scans:
image

Hi,

And does phy-index-fix, use the fp-branch as the reference branch?

This might be about timing. Someone pointed me to an internal discussion about a newer merge overriding issue marking from an older one.

You can’t find it in phy-index-fix?

 
Thx,
Ann

For the phy-index-fix - master branch configured as a reference.


image

Yes, I can’t find it in phy-index-fix branch.

Hi,

Thanks for those details. I’m going to flag this for more expert eyes.

 
Ann