> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/scan-fix-and-prevent/fix/prioritize-issues-for-fixing/using-the-issues-ui/understand-your-issues.md).

# Understand your issues

Snyk Issues works by understanding your vulnerabilities within the context of your application. You can see all the gathered context in the list view of your issues. In the table view, you can see the following details:

* Issue name, which redirects to the Projects page within that issue's Organization.
* Identified risk factors together with the [evidence graph](/scan-fix-and-prevent/fix/prioritize-issues-for-fixing/using-the-issues-ui/evidence-graph.md).
* Exploit maturity
* Asset and source code where the issue is present, together with an access link.
* The Target and Project where the issue is together with an access link.
* The Organization where the issue is present.
* How the scan was performed to identify the issue.
* Which Snyk product was used to perform the scan.

You can also sort the table of issues by these details.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.snyk.io/scan-fix-and-prevent/fix/prioritize-issues-for-fixing/using-the-issues-ui/understand-your-issues.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.