# 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 Community Build 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 instance mode, you can customize a [Understanding measures and metrics](/sonarqube-community-build/user-guide/code-metrics/metrics-definition.md#severity) level for a given software quality or type.
* You can tag and comment on issues.

{% hint style="info" %}
You can receive an email notification for issue-related events: see [Subscribing to notifications](/sonarqube-community-build/user-guide/managing-your-account/subscribing-to-notifications.md).
{% endhint %}

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

* [Issue management solution](/sonarqube-community-build/user-guide/issues/solution-overview.md)\
  This page describes how SonarQube Community Build identifies, assigns, and synchronizes issues, the issue lifecycle, and issue-related features.
* [Retrieving issues](/sonarqube-community-build/user-guide/issues/retrieving.md)\
  This page describes how to retrieve and filter issues.
* [Reviewing issues](/sonarqube-community-build/user-guide/issues/reviewing.md)\
  This page describes how to view and understand your issues in the SonarQube Community Build UI.
* [Editing issues](/sonarqube-community-build/user-guide/issues/managing.md)\
  This page describes how to accept, mark as a false positive, reopen, assign, tag, or comment on an issue.
* [Fixing issues](/sonarqube-community-build/user-guide/issues/fixing.md)\
  This page describes how to get suggested fixes for your issues.
* [Subscribing to notifications](/sonarqube-community-build/user-guide/managing-your-account/subscribing-to-notifications.md)\
  This page describes how to configure your account to receive email notifications for issue-related events.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sonarsource.com/sonarqube-community-build/user-guide/issues/introduction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.