Uploaded image for project: 'SonarQube'
  1. SonarQube
  2. SONAR-10473

Built-in Quality Profile does not keep severity up-to-date

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 6.7.2, 7.0
    • Fix Version/s: 6.7.3, 7.1
    • Component/s: Quality Profile
    • Labels:

      Description

      If a new version of a code analyzer changes the severity of an existing rule, the built-in Quality Profile (provided by this analyzer) is not updated with this new severity when upgrading the analyzer in SonarQube.

      Expected behaviour
      Built-in Quality Profile should be constantly up-to-date with latest default severity (of installed analyzer)

      Steps to reproduce

      • install SonarQube v6.7.2, which ships with SonarJava v4.15, which defines S2077 with Blocker default severity (rule has Blocker severity in the built-in Sonar Way)
      • upgraded to SonarJava v5.1.1 in the Marketplace, which defines S2077 with Critical default severity
      • built-in Sonar Way still has Blocker severity for S2077

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                eric.hartmann Eric Hartmann
                Reporter:
                nicolas.bontoux Nicolas Bontoux
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Due:
                  Created:
                  Updated:
                  Resolved: