> 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-cloud-posture-management/cases-and-issues/investigation-and-response/automation/context-data/issue-context-data.md).

# Issue context data

View context data associated with an issue.

To see context data for an issue, open the issue card and click the **Issue Context Data** icon ![issue\_context\_data\_icon.png](https://1107972533-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHpcayc1yGiwVhvGJ7DK1%2Fuploads%2FTxsc6SeW7xHSRQ8nyNKY%2Fae76e5cb2c8aed2b391a270074eff3eb6bce9358e7ab46680cfbc6a3a6d9be34.png?alt=media\&token=e135f820-f21f-48f1-a7e1-5cd9b2329acc).

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-cloud-posture-management/cases-and-issues/investigation-and-response/automation/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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-cloud-posture-management/cases-and-issues/investigation-and-response/automation/context-data/issue-context-data.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.