SQ Server API returns different Severity than UI

SonarQube Server / Community Build
1

Recently migrated to SQ Dev Edition v2025.1 from an older version of Enterprise
Running a report to pull issues via api (api/issues/search) - api and UI have a mismatch on severity which i believe is related to us running in Multi-Quality Rule Mode

UI
Blocker: 0
High: 6
Low: 78

API
Blocker: 6
High: 0
Minor: 78

Can someone confirm my suspicions? Also, any direction on updating my API calls?

Thanks
Lou

2

Hey @mastersl

What’s the exact API query you’re making, query parameters and all?

3

‘api/issues/search?componentKeys=fhlbny-dev-cm&severities=BLOCKER,CRITICAL,MAJOR,MINOR,INFO&s=SEVERITY&asc=false&ps=500&types=VULNERABILITY&additionalFields=comments&branch=release/2.6’

4

To filter by impact severities in MQR, use the impactSeverities filter. When reviewing the issues returned, ensure you examine the impacts array in each issue’s response, focusing on entries like:

      "impacts": [
        {
          "softwareQuality": "MAINTAINABILITY",
          "severity": "HIGH"
        }
      ],

and not the top-level severity field, such as:

      "severity": "BLOCKER",
5

This addressed it - thank you!

Owe you a beer.

-Lou