# Introduction

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 to someone else.
* 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. See [software-qualities](https://docs.sonarsource.com/sonarqube-server/quality-standards-administration/managing-rules/software-qualities "mention") for more information.
* You can tag and comment on issues.

{% hint style="info" %}
You can receive an email notification for issue-related events: see [subscribing-to-notifications](https://docs.sonarsource.com/sonarqube-server/user-guide/managing-your-account/subscribing-to-notifications "mention").
{% endhint %}

## Related pages <a href="#related-links" id="related-links"></a>

* [solution-overview](https://docs.sonarsource.com/sonarqube-server/user-guide/issues/solution-overview "mention")\
  This page explains how SonarQube Server identifies, assigns, and synchronizes issues, the issue lifecycle, and issue-related features.
* [retrieving](https://docs.sonarsource.com/sonarqube-server/user-guide/issues/retrieving "mention")\
  This page explains how to retrieve and filter issues.
* [reviewing](https://docs.sonarsource.com/sonarqube-server/user-guide/issues/reviewing "mention")\
  This page explains how to view and understand your issues in the SonarQube Server UI.
* [managing](https://docs.sonarsource.com/sonarqube-server/user-guide/issues/managing "mention")\
  This page explains how to accept, mark as a false positive, reopen, assign, tag, or comment on an issue.
* [fixing](https://docs.sonarsource.com/sonarqube-server/user-guide/issues/fixing "mention")\
  This page explains how to get suggested fixes for your issues.
* [triaging-issues-in-sandbox](https://docs.sonarsource.com/sonarqube-server/user-guide/issues/triaging-issues-in-sandbox "mention")\
  This page explains how to triage issues moved to the Sandbox after a SonarQube update.
* [in-devops-platform](https://docs.sonarsource.com/sonarqube-server/user-guide/issues/in-devops-platform "mention")\
  This page explains how to view and manage the security issues reported by SonarQube Server in your DevOps platform.
* [subscribing-to-notifications](https://docs.sonarsource.com/sonarqube-server/user-guide/managing-your-account/subscribing-to-notifications "mention")\
  This page explains how to configure your account to receive email notifications for issue-related events.
* [managing-jira-work-items](https://docs.sonarsource.com/sonarqube-server/user-guide/issues/managing-jira-work-items "mention")\
  Learn how to create Jira work items from Sonar issues.