> 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/cases-and-issues-configuration/customize-issue-fields-and-layouts/issue-layouts.md).

# Issue layouts

Configure Cortex AgentiX issue layouts to control data displayed during issue investigations.

Cortex AgentiX includes default issue layouts. You can add additional issue layouts by installing content packs, duplicating system issue layouts, or creating new custom issue layouts. Issue layouts are applied to incoming issues based on issue layout rules.

Issue layouts control the information displayed in the **Investigate** panel. To see the issue layout that has been applied, in the Issue investigation panel click the **Layout Info** button ![layout-info-button.png](https://404732257-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FocwvgxtzkvBHMLbPsZuG%2Fuploads%2Fgit-blob-92320ae7f1f55c4e42fa0642cd4e26e595fb9aa0%2Fc7c43472effd8964d3a4c434540e76ba09332f7a1ed01c892bf89d3f7fac96d4.png?alt=media) in the upper right corner. Empty layout fields are hidden by default, but are shown if you select **Show empty fields**.

The default issue layouts and any layouts that are added from content packs, are locked by default and cannot be deleted, edited, or exported. To view a system layout, right-click the layout row and select **View**. If you want to edit a system layout, you can detach or duplicate the layout by right-clicking the layout row in the issue layout table and selecting **Detach** or **Duplicate**. If you detach a layout, the layout does not receive content updates until it is reattached. To reattach a system layout, right-click the layout row and select **Attach**. If you detach a layout and make changes, those changes may be overwritten if you later reattach the layout. If a layout is detached, you can edit or duplicate it, but you cannot delete or export it. If you instead duplicate the issue layout, the new duplicated layout can be edited, deleted, or exported, the same as a custom issue layout.

When viewing an issue, most issue fields can be edited inline, by users with editing permissions. After editing a field inline, click the check mark to save your change. Some system fields, such as **Source Instance**, cannot be edited.

To modify an existing custom layout, go to **Settings** → **Configurations** → **Object Setup** → **Issues** → **Layouts**, right-click the layout in the layouts table, and select **Edit**, **Duplicate**, **Delete**, or **Export**.


---

# 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-agentix/configure-cortex-agentix/cases-and-issues-configuration/customize-issue-fields-and-layouts/issue-layouts.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.