Showing content from https://docs.sonarsource.com/sonarqube-server/latest/user-guide/issues/introduction/ below:
Issues | SonarQube Server Documentation
Latest | User guide | Managing issues | Introduction
Managing your code issues
An automated code review detects an issue as a problem in your code. When a coding rule is broken, an issue is raised. The issue affects one or more software qualities with a varying impact level, called severity, as inherited from the rule.
The following applies:
- A new issue is automatically assigned to the last committer on the issue line - the author - if the author can be correlated to a SonarQube Server user. You can reassign the issue.
- The issue context locates the issue in the code. The primary location is where the issue message is displayed. Secondary locations may be shown to help you understand the issue. Paths through the code (execution flows) are shown from the source to the destination (sink) when the issue originated upstream.
- An issue is assigned a status that changes during its life cycle. In particular:
- You can accept an issue to fix it later (status: Accepted).
- With the corresponding authorization, you can set an issue to False positive if you think the analysis is mistaken.
- Depending on the metrics mode, you can customize a severity level for a given software quality or type.
- You can tag and comment on issues.
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4