We are using Developer Edition v2025.3.1, our code is in Gitlab. A developer has an issue in his branch, in this case a complexity too high. After a review the issue has been accepted, no more issues. Then his branch was merged into a release branch, and the issue was back. The issue id in Sonarqube, visible in the url, though, was a different one. Somehow it was opened again. We had to accept the issue again in the release branch.
Any hints why the acceptance does not survive a merge request?
Did you perform a PR analysis when the developer wanted to merge his code? This is how issues statuses are “carried” between branches.
Hey @Colin, thanks for this info, I tried to reproduce the situation in a test setup, and it works as expected. In the failure case, a PR analysis was done. The situation, though, was different, since several branches were merged to a release branch, and somehow one of the other branches introduced the accepted bug again with another id. I will be triggered early when the situation appears again and will analyze any tiny detail what the developers are doing. Thanks so far, when I know more I will post again.