User “system” automatically reactivates rule in extended profile

Similar to this topic User “system” automatically reactivates rule upon restart - SonarQube Server / Community Build - Sonar Community

but on SonarQube Cloud.

After the updates of SonarWay profile on September 22nd, we extended the JavaScript profile and deactivated rule S7740 in the extended profile.

On September 26 the SonarWay profile saw many updates again. The changelog on our extended profile shows that S7740 was activated again in our extended profile.

This shouldn’t happen and make the use of extended profiles useless for us.

  • ALM used: Azure DevOps
  • CI system used: Azure DevOps
  • Languages of the repository: JavaScript
  • Steps to reproduce
    • Extend the SonarWay profile
    • Deactivate a rule
    • Wait for the system user to activate it again
  • Potential workaround: unknown

Hey @calle2010

We had to rollback an analyzer deployment (which would have deactivated the rule), but I’m surprised that it was reactivated when we redeployed the rule. I’ve flagged this for the team.

1 Like

Hello @calle2010

We reviewed the case, and as Colin already mentioned, the rule got reactivated, as it was recreated as new one after an analyzer rollback-redeploy.

As of today, we’ve decided not to make any changes, as this situation appears to be an isolated occurrence and regular rule update does not affect the rules deactivated by the user.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.