Accepted Issues resurface after SonarQube version upgrade

  • which versions are you using: Enterprise Edition v2025.3 (108892)
  • how is SonarQube deployed: zip
  • what are you trying to achieve: Accepted issues should not get re-opened automatically.
  • what have you tried so far to achieve this: Old Accepted issues are getting reopened on SonarQube upgrade.

We have many existing issues in code in Accepted state. These issues are getting reopened automatically if there is a change in the SQ rule associated with the issue during SQ version upgrade.
This is causing a lot of manual work as we have to again Accept these bugs after a new scan.

Is there a option to avoid this redundant work that has to be done on each SQ version upgrade?

Hey @jeninjames

Can you share an example of one of these issues? Do you see anything in the changelog of the issue, like:

Automatically reopened because the vulnerability flow changed.

Hello @Colin,

I’m facing the same issue on my SonarQube Application as well, But the only difference is the version I’m currently in.
I had Upgraded from v10.8.1 to 2025.1 LTA.

Could you please assist me on how to check the changelog of an issue ?
I’m not sure if it’s the activity tab of the particular issue, which you’re referring to.

Thanks in advance for your inputs !

That would be it!

And again, specific examples are super helpful here.

I’ll share the details if we face the issue again in future upgrades. I tried getting few samples from accepted issues, but it was a big list and couldn’t get the recently accepted one. Is there a way to get the issues whose status was changed recently ?