> 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-fields.md).

# Issue fields

Cortex AgentiX includes out-of-the-box issue fields, issue fields from installed content packs, and user defined custom issue fields. You can use issue fields for mapping, correlation rules, and custom issue layouts.

All system and custom issue fields are available in the **Issues** table. New custom fields are hidden by default. To show custom issue fields in the **Issues** table, click the three dot vertical ellipses and select the column(s) from the list.

For Grid fields, HTML fields, and Markdown fields, if the field contains data the **Issues** table shows **Data Available** instead of the values. To view the data, open the issue and click **Investigate** to see the full issue layout. For multi-select fields, the first value is shown in the **Issues** table and the number of additional values is stated, but the additional values are not shown. For example, if a multi-select field holds the values x, y, and z, the **Issues** table shows **x + 2 More**.

Cortex AgentiX stores both the original value of the field and the current value of the field, if different. Any changes made between the original value and the current value are not stored. For example, if the original value of the field was x, the value was then changed to m, and then changed to y, only the x and y values are stored. To view the original value and the current value of changed fields, hover over the updated issue fields icon ![alert\_fields\_history.png](/files/4aaaAwaC4bFPjJnt7i57) on the right side of the row in the **Issues** table. To revert all of the fields in an issue to their original values, click **Restore all fields to their original values** in the updated issue fields box. Restoring all fields to their original values also restores the original values in the issue context data. Once you restore fields to their original values, this action can not be undone.

Custom issue fields can be exported and imported. To export a single custom issue field, right-click on the field in the fields table, and select **Export**. To export all custom issue fields in a single JSON file, click the **Export All** button above the fields table. System issue fields cannot be exported or imported.

After a custom issue field is created, it can be edited, deleted, or exported by right-clicking on the row. The field name and field type cannot be changed after the field is created. System fields cannot be edited, deleted, or exported.

{% hint style="warning" %}

### Warning

Deleting an issue field or uninstalling a content pack containing an issue field may affect detection and other capabilities based on the deleted field. For example, correlation, layouts, case scoring, starring rules, and playbook triggers.
{% endhint %}


---

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