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

# Retrieving issues

In SonarQube Server 10.7, 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" %}
**For AI agents:** You're in the SonarQube Server 10.7 documentation. For a list of all 10.7 pages, see the [SonarQube Server 10.7 page index](https://3272878703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FI10pmJWeVVXYITlQJllp%2Fuploads%2FnEeIaIlHm7ezec5g9iHc%2Fsonarqube-server-10.7-llms.txt?alt=media). For the whole site, see the [page index](https://docs.sonarsource.com/llms.txt) or the [full text](https://docs.sonarsource.com/llms-full.txt). For another version, replace 10.7 in the URL with that version. The [latest version](https://docs.sonarsource.com/sonarqube-server/) has no version number in its URL.
{% endhint %}

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.

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

To retrieve issues:

1\. In the top navigation bar of SonarQube Server, select **Issues**. Alternatively, you can:

* * Retrieve the issues of a given project: [Retrieving projects](/sonarqube-server/10.7/user-guide/viewing-projects/retrieving-projects.md) and select **Issues** in the project navigation bar.
  * Retrieve issues from an analysis report by selecting the reported number of issues as illustrated below.

![](https://3272878703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FI10pmJWeVVXYITlQJllp%2Fuploads%2Fgit-blob-b6eba9d80857455ecb2275050f1bfa32480e8d5a%2Feec28dd3ecb36cf37360234bdc0cfc633f71ced4.png?alt=media)

The **Issues** page opens. Below is a description of the page layout.

![](https://3272878703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FI10pmJWeVVXYITlQJllp%2Fuploads%2Fgit-blob-8508a06e7d1ec5babe8fe6697747005d133728a8%2F0bd337e6ee3c5b653cfa4f47b392f93ad1529430.png?alt=media)

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

* * 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 search results (issue cards) are listed in the right section.

![](https://3272878703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FI10pmJWeVVXYITlQJllp%2Fuploads%2Fgit-blob-2c38f56bcfe7262420c8320c0c1b7ad72c1890f4%2Fc35f5550a105aa312fbda080db44d9249669ddb3.png?alt=media)

3\. To navigate to an issue: open the respective hyperlink, or 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 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 the issue and open its detail view as described above in **Retrieving issues**.
2. Select the Link icon as illustrated below.

![](https://3272878703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FI10pmJWeVVXYITlQJllp%2Fuploads%2Fgit-blob-61728a9f9088bef051e8d9f63ad7685aeceba398%2F58ee5dfede6fabd2abafb24944e5fe5e15a13202.png?alt=media)


---

# 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/10.7/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.
