> 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/configure-cortex-xsiam/customize-cases-and-issues/customize-issue-fields-and-layouts/issue-fields/create-custom-issue-fields.md).

# Create custom issue fields

Create and manage custom Cortex XSIAM issue fields for JSON mapping, XQL correlation rules, issue layouts, and automation.

Create custom Cortex XSIAM issue fields to map incoming data, support correlation rules, and tailor issue layouts. You can use custom fields to:

* Map raw JSON fields from incoming issues.
* Display custom field data in the **Issues** table.
* Create correlation rules that generate issues from XQL queries.
* Map XQL query output to custom issue fields.
* Design custom issue layouts that include custom fields.

### Create a custom Cortex XSIAM issue field

1. Select Settings → Configurations → Object Setup → Issues → Fields → New Field.
2. Choose a field type and enter a field name. For available field types, see [Issue field types](/cortex-xsiam/configure-cortex-xsiam/customize-cases-and-issues/customize-issue-fields-and-layouts/issue-fields/issue-field-types.md). You can add an optional tooltip for users.

   If you add a grid, see [Create a grid field for an issue](/cortex-xsiam/configure-cortex-xsiam/customize-cases-and-issues/customize-issue-fields-and-layouts/issue-fields/create-a-grid-field-for-an-issue.md).
3. Click Save.

### Import, export, and update custom issue fields

Import and export custom issue fields. To export one field, right-click it in the fields table and select **Export**. To export all custom fields as one JSON file, click **Export All** above the table.

After you create a custom issue field, right-click its row to edit, delete, or export it. You cannot change the field name or field type.

Update custom field values with the **Set** command in the CLI, a script, or a playbook. For more information, see [Update issue fields](/cortex-xsiam/detect-investigate-and-respond-to-threats/investigation-and-response/investigate-issues/issue-investigation-actions/update-issue-fields.md).


---

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