> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-cloud/managing-your-projects/issues/retrieving.md).

# Retrieving issues

Retrieving issues in SonarQube Cloud is the first step to finding code security and maintainability problems in your code base.

You can retrieve and view the issues detected during a project’s analysis. Ensure you have proper [Introduction](/sonarqube-cloud/managing-your-projects/issues/introduction.md#issues-permissions) on a project to view and administer the issues.

{% hint style="info" %}
Issues can also be reported in your DevOps platform. For more information, see [In your DevOps platform](/sonarqube-cloud/managing-your-projects/issues/in-devops-platform.md).
{% endhint %}

## Retrieving issues <a href="#retrieving" id="retrieving"></a>

Retrieve issues in one of these ways:

* Select **Assigned issues** in the top navigation bar. **Assigned issues** lists all issues assigned to you.

<div align="left"><figure><img src="https://2223713658-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FB4UT2GNiZKjtxFtcFAL7%2Fuploads%2Fgit-blob-38256ccf046768284aef053c341c91f217704ca7%2Fsonarqube-cloud-assigned-issues.png?alt=media" alt="Assigned issues page in SonarQube Cloud opened from the top navigation bar, with Filters, the sort list, and the applied status filters above the issue list."><figcaption></figcaption></figure></div>

* In a project, go to **Analysis** > **Issues**.

<div align="left"><figure><img src="https://2223713658-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FB4UT2GNiZKjtxFtcFAL7%2Fuploads%2Fgit-blob-f26518341f1f00b68d585fdd0c7901771888fcb2%2Fsonarqube-cloud-project-issues.png?alt=media" alt="Issues page of a project in SonarQube Cloud opened from the side navigation, with Top issues selected, the applied filters, and the issue list."><figcaption></figcaption></figure></div>

* In a project, go to **Analysis** > **Summary**, select the branch or pull request next to the page title, then select a number of open issues on the **New code** or **Overall code** tab.

<div align="left"><figure><img src="https://2223713658-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FB4UT2GNiZKjtxFtcFAL7%2Fuploads%2Fgit-blob-dffe7c03c20a1e4df376537a096c293a8e39b2fa%2Fsonarqube-cloud-project-summary-issues.png?alt=media" alt="Summary page of a project in SonarQube Cloud showing the quality gate status and open issue counts for Security, Reliability, and Maintainability."><figcaption></figcaption></figure></div>

* If your organization belongs to an enterprise, open the **Issues** page of your organization.

## Using the Issues page <a href="#using-the-issues-page" id="using-the-issues-page"></a>

The **Issues** page of a project opens with:

1. The **Top issues** and **All issues** toggle. By default, the page lists top issues. For more information, see [#top-issues](#top-issues "mention").
2. **Filters**, which opens the list of filter categories. For more information, see [#filtering-issues](#filtering-issues "mention").
3. The sort list, which shows **Sort by Priority** by default. For more information, see [#sorting-issues](#sorting-issues "mention").
4. **Applied filters**, which lists the filters in use.
5. The issue results. Organization members can also select issues and change them in bulk. For more information, see [Editing issues](/sonarqube-cloud/managing-your-projects/issues/editing.md#editing-issues-in-bulk).

<div align="left"><figure><img src="https://2223713658-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FB4UT2GNiZKjtxFtcFAL7%2Fuploads%2Fgit-blob-1090d6b32863809d826437bf2927c24bc2d8182e%2Fsonarqube-cloud-issues-page.png?alt=media" alt="Issues page of a project in SonarQube Cloud with the Top issues toggle, the Filters button, the sort list, the applied filters, and the issue results."><figcaption></figcaption></figure></div>

The **Issues** page of an organization and the **Assigned issues** page show **Filters** and the sort list, but not the **Top issues** and **All issues** toggle.

### Top issues <a href="#top-issues" id="top-issues"></a>

On the **Issues** page of a project, use the toggle above the search results to switch between two lists:

* **Top issues**: Lists Security and Reliability issues with Blocker, High, or Medium severity and the Open or Confirmed status. When a project has no top issues, the toggle shows **No top issues** and the page lists all issues instead.
* **All issues**: Lists all issues with the Open or Confirmed status.

The number next to each option shows how many issues it lists. Selecting an option replaces the filters in use. If you change the filters afterward, neither option is selected.

### Filtering issues <a href="#filtering-issues" id="filtering-issues"></a>

Select **Filters**, select a category, and then select the values to filter by. The number next to **Filters** shows how many values are selected.

The following filter categories are available:

* **Software quality**: Security, Reliability, and Maintainability.
* **Severity**: Blocker, High, Medium, Low, and Info.
* **Code attribute**: Consistency, Intentionality, Adaptability, and Responsibility.
* **Status**: Open, Confirmed, False positive, Accepted, and Fixed.
* **Compliance category**: The compliance and security standards that the issues relate to.
* **Creation date**: **Overall code**, **New code**, or a date range in which the issues were created.
* **Language**: The languages of the files with issues. You can search for a language.
* **Rule**: The rules that raised the issues. You can search for a rule.
* **Tag**: The tags added to the issues.
* **Directory** and **File**: The location of the issues in your code.
* **Project**: The projects that the issues belong to. This category is available on the **Issues** page of an organization.
* **Assignee**: The users that the issues are assigned to.
* **Author**: The authors of the code that raised the issues.

The filters in use are listed in **Applied filters**. To remove a filter, select the close icon on it. To reset the filters to the default (the Open and Confirmed statuses), select **Clear filters**.

* To retrieve only the issues in new code, select **Filters** > **Creation date** > **New code**.
* To retrieve the issues assigned to you, select **Filters** > **Assignee** > **Assigned to me**.
* To retrieve unassigned issues, select **Filters** > **Assignee** > **Not assigned**.

### Sorting issues <a href="#sorting-issues" id="sorting-issues"></a>

Use the sort list above the search results to change the order of the issue cards:

* **Sort by Priority**: Lists the issues that matter most first. This is the default order.
* **Sort by File name**: Groups issues by file and orders them by line number.
* **Sort by Creation date**: Lists the newest issues first.

Your browser remembers the selected order for your next visit. Clearing the filters or switching between **Top issues** and **All issues** keeps the selected order.

#### How Priority orders issues <a href="#priority-order" id="priority-order"></a>

Issues are listed in this order:

1. Security and Reliability issues, from highest to lowest severity. At the same severity, Security issues come before Reliability issues.
2. Maintainability issues, from highest to lowest severity.

If an issue impacts more than one software quality, its highest-ranked impact sets its position. Issues with the same priority are ordered by file and line number.

### Issue card <a href="#issue-cards" id="issue-cards"></a>

Each issue card contains information that helps you identify the following:

1. The name of the rule that triggered the issue.
2. Impacted software quality and severity level.\
   For more information, see [SonarQube rules](/sonarqube-cloud/standards/managing-rules/rules.md#software-qualities).
3. Status of the issue.
4. Assignee
5. Code attribute\
   For more information, see [SonarQube rules](/sonarqube-cloud/standards/managing-rules/rules.md#code-attributes).
6. Tags
7. Additional information: line number, estimated time effort to fix the issue, and the amount of time that has passed since the introduction of the code.

<div align="left"><figure><img src="https://2223713658-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FB4UT2GNiZKjtxFtcFAL7%2Fuploads%2Fgit-blob-c9abb883bba679c978a0f3431c75fdecf9263fe4%2Fsonarqube-cloud-issue-card.png?alt=media" alt="Issue card in SonarQube Cloud showing the rule message, software quality and severity, status, assignee, code attribute, tags, line, effort, and age."><figcaption></figcaption></figure></div>

## Navigating issues <a href="#issues-navigating" id="issues-navigating"></a>

To navigate to an issue, select the issue card in the search results and press the Right arrow key or click on its name. A detail view of the issue opens in the right section, and the left sidebar shows the search results. To start a new search, press the Left arrow key or navigate one step back in your browser.

## Copying the URL of an issue <a href="#copying-url" id="copying-url"></a>

1. Retrieve an issue and navigate to the issue’s detail page.
2. Click on the link icon next to the name of the issue to copy the issue’s URL.

<div align="left"><figure><img src="https://2223713658-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FB4UT2GNiZKjtxFtcFAL7%2Fuploads%2Fgit-blob-47a10f8cb0e3fe2995734a49ef47ab3273ffb82f%2Fsonarqube-cloud-issue-copy-url.png?alt=media" alt="Issue detail page in SonarQube Cloud with the link icon next to the issue title, the issue list on the left, and the issue details on the right."><figcaption></figcaption></figure></div>

## Related pages

* [Editing issues](/sonarqube-cloud/managing-your-projects/issues/editing.md#tagging)
* [Editing issues](/sonarqube-cloud/managing-your-projects/issues/editing.md#assigning)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sonarsource.com/sonarqube-cloud/managing-your-projects/issues/retrieving.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.