Overview | |
---|---|
Definition (Hover Text) | highlight count of issues that exist every time a piece of code breaks a coding rule. The set of coding rules is defined through the associated Quality profile for each programming language in the project |
Source Tools | SonarQube, Sonar Cloud |
Graph type | Line |
Filters | Sonar Project |
Hover Format on KPI | Date Range: Blocker: <<Value>> Critical: <<Value>> Major: <<Value>> Minor: <<Value>> Info: <<Value>> |
Fields on Overlay | Project Job Name Sonar Violations Weeks |
Business Logic | |
Calculation Formula | Its directly calculated in Sonarqube |
Trend | Higher the violations, lower is the Quality |
Maturity Levels | - |
Instance level thresholds | - |
Configurations | |
Processor Fields | NA |
KPI Specific fields | NA |
How to Validate KPI | |
Suggested ways of working | |
Sample JQLs | |
Benefits of KPI | |
How does the KPI help | The Sonar Violation KPI helps teams improve code quality by identifying and tracking violations of coding standards and best practices. It enables early detection of potential issues, reduces technical debt, and enhances maintainability of the codebase. By addressing violations, teams can improve overall code quality, reduce bugs, and increase development efficiency. |
Page Comparison
General
Content
Integrations