The Severity filter in the UI remains disabled with the message “Severity is available after a new analysis occurs” even after completing new analyses.
Steps to Reproduce
Navigate to project in SonarQube UI
Run a new analysis on the project
Wait for analysis to complete
Attempt to use the Severity filter
Filter remains disabled with message “Severity is available after a new analysis occurs”
Expected Behavior
The Severity filter should become enabled after a successful analysis, allowing filtering of issues by severity level.
Questions
Are there specific permissions required for the Severity filter to become active?
Are there any known conditions that could cause this filter to remain disabled?
Template for a good new topic, formatted with Markdown:
ALM used = GitHub
CI system used = Jenkins CI/CD
Scanner command used when applicable = scan was completed
Languages of the repository = AngularJS, NestJS
Only if the SonarCloud project is public, the URL = private project
Error observed (wrap logs/code around with triple quotes ``` for proper formatting) = when I mouse over the Severity option on Issues page > Filters > Severity, it was grey out and tooltip was showing : “Severity is available after a new analysis occurs.”
Steps to reproduce = Those filter options were suddenly become inactive since last Friday, 3rd Jan 2025. We are not sure what could cause this.
Potential workaround
Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!