Issues

An issue is a problem in your code that prevents it from being Clean Code. Each Clean Code attribute is evaluated, for a given language, based on a series of rules. 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 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.
• You can tag and comment on issues.

Related pages

• Issue management solution overview
  This page explains: how SonarQube identifies, assigns, and synchronizes issues; the issue lifecycle; and issue-related features.
• Reviewing issues
  This page explains how to retrieve, view, and understand your issues in the SonarQube UI.
• Managing issues
  This page explains how to accept, mark as False positive, reopen, assign, tag, or comment on an issue.
• Configuring your notifications for issue-related events
  This page explains how to configure your account to receive email notifications for issue-related events.
• Viewing and managing security issues in your DevOps platform
  This page explains how to view and/or manage the security issues reported by SonarQube in your GitHub or GitLab instance.