> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-agentix/configure-cortex-agentix/automations/context-data/issue-context-data.md).

# Issue context data

To see context data for an issue, open the issue card and click the **Issue Context Data** icon ![issue\_context\_data\_icon.png](/files/L8xxvqFXYf7KjzGGnKPM).

Consider the following information when working with context data:

* When an issue is created, the issue field data is stored under the `issue` key in the context data. When an investigation is opened and commands are run, the data returned from those commands is stored outside of the main `issue` key.
* Issue context data is split into two tabs. The **Issue** tab contains the context data from the issue fields and the commands run on the issue. The **Case** tab contains the parent case fields and other case data. None of this data is added to the context data for the parent case unless you add it.
* You can add keys and values to the context data. This is useful when developing playbooks, and other automations. For more information, see [Add context data to an issue](/cortex-agentix/configure-cortex-agentix/automations/context-data/add-context-data-to-an-issue.md).
* When running automations on an issue, the issue can access context data from its parent case; however, it cannot access context data from other issues. If you want to use context data from other issues, add it to the parent case.

***


---

# 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://cortex-docs.paloaltonetworks.com/cortex-agentix/configure-cortex-agentix/automations/context-data/issue-context-data.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.