Suggest new features

New features Think the latest versions could be improved in some way ? Come see if your idea is already shared by others, and make more suggestions that you think could benefit the overall community (beyond your specific case). New rules Suggest new rules that could enrich one (or many !) of the <a href="">SonarSource code analyzers</a> .
About the Suggest new features category [Suggest new features] (1)
Better support for community edition in the Azure pipeline tasks [New features] (1)
Extenability of S2699? (Tests should include assertions) [Suggest new features] (5)
Sonar-scanner client: use in-sensitive cases for file path patterns [New rules] (1)
Backup Extended Description of Rules [New features] (5)
Support Dependency Checks for Known Vulnerabilities [New features] (5)
Organization level PATs [New features] (2)
Add Delphi language support [New features] (3)
Java Rule - double if block instead of elseif [New rules] (2)
Generic Code Coverage should be skipped when coverageReportPaths file does not exist instead of fail scan [New features] (1)
Bean Validation should be enabled [New rules] (9)
REST api to request quality gate status by branch? [New features] (2)
Provide links to SCM to view repo/commit/file directly from SonarQube screens [New features] (1)
Allow adding custom selectors for CSS S4670 [New rules] (1)
Making test coverage measures mode useful [New features] (3)
Feature request: Add brakeman sensor to Ruby plugin [New features] (2)
Sonarlint for PLSQL code [Suggest new features] (5)
Java bug using Collectors::toMap() with ArrayList::new [New rules] (5)
Vs Code Warning vscode.previewHtml [Suggest new features] (1)
[TRANSPARENCY] Disable default server info collect by SonarSource [New features] (4)
Would Like to Contribute Internationalization Rule Sets [New rules] (8)
Typescript TODO Rule [Suggest new features] (1)
Check licenses of dependencies [New features] (2)
Add SQ parameter for callback URL [Suggest new features] (2)
User administration / security: Delete an user from SonarQube database [New features] (2)
C# There should be a rule for using TryAdd(), TryParse() etc. and not checking the results [New rules] (2)
New lines will point to added lines [Suggest new features] (1)
Allow marking duplications as "false-positives"/"won't fix" [New features] (3)
If operator in VB casts Nothing to type-default instead of nullable of that type [New rules] (2)
Housekeeping / Database Cleaner / version event handling [Suggest new features] (8)