Automatically reopened issues after upgrade

SonarQube Server / Community Build
1

Must-share information (formatted with Markdown):

  • which versions are you using (SonarQube Server / Community Build, Scanner, Plugin, and any relevant extension):- Enterprise v2025.1 (102418)
  • how is SonarQube deployed: zip, Docker, Helm:- Zip
  • what are you trying to achieve:- Issues reopened
  • what have you tried so far to achieve this

Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!

We have upgraded our Sonar Qube from 9.93 to V2025.1. After upgrade we found many issues reopened which were closed in previous version.

Here is the Log :-

# Change this code to not log user-controlled data.

Logging should not be vulnerable to injection attacks[roslyn.sonaranalyzer.security.cs:S5145](https://sonarqube.bluebayinvest.com/coding_rules?open=roslyn.sonaranalyzer.security.cs%3AS5145&rule_key=roslyn.sonaranalyzer.security.cs%3AS5145)

*** April 1, 2025 at 12:42 AM**


Automatically reopened because the vulnerability flow changed.

*** April 1, 2025 at 12:40 AM**

Status changed to OPEN (was ACCEPTED)

* February 10, 2025 at 4:07 PM

N


added a comment

Data is not user-controlled

*** February 10, 2025 at 4:06 PM**

N


Resolution changed to WONTFIX

Status changed to RESOLVED (was OPEN)

Any idea, this was closed in previous version.

Thanks
Sunil Bindra

2

Hi,

Here you go:

You (someone in your team) had manually marked the issue as Won’t Fix based on the information available at the time, and made the comment that

But then something changed in the code (or possibly the rule got smarter). With new information, you may not make the same judgement. So the system automatically reopened the issue so that you could re-examine the new circumstances.

 
Ann

5

Is there any log what rules are changed due to which his happens. this is giving us wrong information across al projects and metrics gone all wrong.

Thanks
Sunil

6

Hi Sunil,

Check the Quality Profile change log to see rule changes.

 
HTH,
Ann

7

Hi Ann,

So following your documentation Issues, when an Issue is marked as ‘Accept’, we need to also mark the issue as ‘False Positive’.

To confirm, does this step stop reopening of manually closed issues in upgrades please?

Thanks
Sunil Bindra

8

Hi Sunil,

It’s either Accept or False Positive. Both are issue statuses. If you choose them in sequence, you simply overwrite the old status with the new one.

No. Again:

 
HTH,
Ann