> 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/user-guide/issues/reviewing.md).
# Reviewing issues
Navigate and review issues raised by automated code review and analysis in SonarQube Server 2026.5.
SonarQube highlights the specific lines of code associated with identified issues.
To view an issue in the code:
1. Retrieve the issue and open its detail view. See [Retrieving issues](/sonarqube-server/user-guide/issues/retrieving.md) for more information.
2. In the **Where is the issue?** tab, you can see the issue’s location with the issue message.
a. **Where is the issue?** tab\
b. Code that raised the issue.\
c. Issue message shown in code.
3. Depending on the issue, secondary locations or execution flows may be displayed to help you understand it or trace its source. To navigate through the secondary locations or the issue flow, see [#secondary-locations](#secondary-locations "mention").
4. To understand why this is an issue, open the **Why is this an issue?** tab in the issue description. You can also open the rule that raised the issue by selecting the rule link at the top of the issue description.
## Navigating through the issue’s secondary locations
All SonarQube Server issues specify a location in the code showing where the issue occurs. However, some of the more complex rules produce issues for which a single location is not enough to adequately explain why the issue has occurred. These more complex rules often identify additional locations in the code to help understand the problem. These additional locations are referred to as secondary locations. Secondary locations may just indicate other locations that are related to the issue or may identify a flow through the code that leads to the issue.
### Other locations
To navigate through the other locations of an issue:
1. Retrieve the issue and open its detail view. See [Retrieving issues](/sonarqube-server/user-guide/issues/retrieving.md) for more information.
2. **Where is the issue?** tab opens.
3. The secondary locations are listed in the left side bar as well as in the code view.
4. To navigate to a secondary location, click on it in the list. You can also use Alt/Option + up and down arrows keyboard combination to navigate the code locations.
### Execution flow
When the issue originates upstream, paths through the code (execution flows) are shown from the source to the sink (destination). In particular, for issues breaking a security-injection rule, there is a vulnerability when the inputs handled by your application are controlled by a user (potentially an attacker) and not validated or sanitized. In that case, SonarQube Server displays the execution flow from the sources (user-controlled inputs) to sinks (sensitive functions).
To navigate through the execution flow of an issue:
1. Retrieve the issue and open its detail view. See [Retrieving issues](/sonarqube-server/user-guide/issues/retrieving.md) for more information.
2. **Where is the issue?** tab opens.
3. The execution flows are listed in the left side bar indicating the execution flow across multiple files.
4. To navigate to a location in the execution flow, select it in the list. You can also use Alt/Option + up and down arrows keyboard combination to navigate the code locations.
## Viewing the issue management history and comments
1. Retrieve the issue and open its detail view. See [Retrieving issues](/sonarqube-server/user-guide/issues/retrieving.md) for details.
2. Open the **Activity** tab. The tab displays the number of comments for the issue.
3. Click the **Add a comment** button to create a new one.
---
# 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/user-guide/issues/reviewing.md?ask=&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.
.png)
.png)