> 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-server/2026.2/user-guide/issues/retrieving.md).

# Retrieving issues

In SonarQube Server 2026.2, retrieve and view detected issues after your project's analysis.

You can retrieve and view the issues detected during the analysis of any public project. For a private project, you need the Browse permission on the project.

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

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

Select **Issue** in the top navigation bar. Alternatively, you can retrieve issues from the side navigation of a project, application or portfolio.

<figure><img src="https://2744305742-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3VWSqvZ4eaBLWvA6epdv%2Fuploads%2FiVxuVPPHROC3bpIv8VTh%2Fissues-top-nav.png?alt=media&amp;token=ed0afcd9-4760-48a5-aa3f-989b5362244f" alt="Retrieving issues from the top navigation bar"><figcaption></figcaption></figure>

You can also retrieve issues from the analysis report located on the Overview page of a project, application or portfolio by selecting the reported number of issues on the new or overall code cards.

<div align="left"><figure><img src="https://2744305742-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3VWSqvZ4eaBLWvA6epdv%2Fuploads%2FhohV4RmLuhKgcfQSA3pM%2Fissues-quality-gate%20(1).png?alt=media&amp;token=08c5ca3e-0269-455d-828d-210420fc4991" alt="Retrieving issues from the overview page of a project, application or portfolio."><figcaption></figcaption></figure></div>

The **Issues** page opens with:

1. Filters in the left-side panel.
2. Issue results in the right section of the page.

<div align="left"><figure><img src="https://2744305742-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3VWSqvZ4eaBLWvA6epdv%2Fuploads%2FJ3ukvgJ7zD7iCVOqPpCv%2Fissues-sections%20(1).png?alt=media&amp;token=e536de85-15e1-49c4-aeac-116dcbc76833" alt="The issues page"><figcaption></figcaption></figure></div>

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

In the **Filters**, enter your search criteria to filter the list of issues.

* To retrieve only the new issues (issues detected in new code), select **Issues in new code** at the top of the **Filters** section.
* To retrieve the issues assigned to you, select **My Issues** at the top of the **Filters** section.
* To retrieve unassigned issues, select **All** at the top of the **Filters** section, open the **Assignee** filter, and select **Not assigned**.

The issue cards are listed in the search results in the right section. An issue card contains the following information:

<div align="left"><figure><img src="https://2744305742-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3VWSqvZ4eaBLWvA6epdv%2Fuploads%2FT7Jax0eA34ee2YoPieBk%2Fissues-card-details.png?alt=media&amp;token=ba36966f-93c1-4ba3-b2a7-0958e59e4d6c" alt="The issue card details"><figcaption></figcaption></figure></div>

1. Project name and the path to the code file.
2. The name of the rule that triggered the issue.
3. Impacted software quality (in MQR mode) or type (in Standard Experience) and severity level.
4. Status of the issue.
5. Assignee
6. Coding attribute
7. Tags
8. Additional information: line number, estimated amount of time to fix the issue, the amount of time that has passed since the introduction of the code.

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

To navigate to an issue select the issue card in the search results and press your Right arrow key. The detail view of the issue opens in the right section, and the search results are shown in the left sidebar. 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 the issue and open its detail view.
2. Select the link icon located next to the title.

<div align="left"><figure><img src="https://2744305742-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3VWSqvZ4eaBLWvA6epdv%2Fuploads%2FxBGNNCGHOJ6CRiJeUeQB%2Fissues-link.png?alt=media&amp;token=408eb051-c102-4577-a1d1-f2a2ee931736" alt="Link to the issues"><figcaption></figcaption></figure></div>


---

# 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-server/2026.2/user-guide/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.