> 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-xsiam/detect-investigate-and-respond-to-threats/investigation-and-response/analyze-and-resolve-cases/analyze-case-details/issue-feed.md). # Issue feed Review the case issue feed in Cortex XSIAM to trace case activity chronologically. In Cortex XSIAM, the issue feed provides a chronological visualization of the case lifecycle, highlighting key case information from initial detection to the most recent activity. Key features include: * **Issue count:** See the total number of issues linked to the case. * **High level details:** Review issue details in the timeline, or click an issue to open the full issue card. When an issue is resolved, the issue status and title is dimmed. * **Contextual insights:** View integrated insights directly within the timeline (when available), providing extra layers of intelligence on why specific events were flagged. * **Unified progression:** Gain immediate clarity on the speed of an attack, helping you distinguish between rapid automated threats and slow-moving lateral movement. * **Group issues by attribute:** Sort the issues in the timeline with the **Group By** option that allows you cluster issues and insights by selected criteria, such as category, severity, detection method, or detection rule. * **Browse issues in the feed:** Open an issue and use the arrows in the top left corner to browse through the issue cards. --- # 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-xsiam/detect-investigate-and-respond-to-threats/investigation-and-response/analyze-and-resolve-cases/analyze-case-details/issue-feed.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.