> 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-xdr-5.x/detect-investigate-and-respond-to-threats/investigate-and-respond-to-cases/investigate-issues/issue-investigation-actions/create-a-featured-field.md).

# Create a featured field

To help you to track issues involving specific hosts, users, and IP addresses, you can label specific issue attributes as featured fields. Issues that contain a matching featured field value are identified with a ![featured-alert-field-flag.png](/files/xMbuXbWl6OhtAVdMHOub) flag in the **Name** field of the **Issues** table. After setting up featured fields, you can use them filter the **Issues** table and to create case scoring rules.

Note: Featured Active Directory values are displayed in the **User** and **Host** fields accordingly.

### How to create a featured field

1. Go to Cases & Issues → Case Configuration → **Featured Fields** and select a type of featured field.
2. Click **Add featured \<field-type>** and select one of the following options:
   * **Create New**

     To create a new featured field from scratch, enter one or more field-type values and click **Add**.
   * **Upload from File**

     To upload field values from a CSV file, upload your file and click **Import**. Click **Download example file** to ensure you are using the correct format.
3. Find issues containing featured fields.

   In the **Issues** table, use the **Contains Featured** filters.
4. (Optional) Create a case scoring rule using the **Contains Featured** fields to further highlight and prioritize issues containing the Host, User, and IP address attributes.


---

# 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-xdr-5.x/detect-investigate-and-respond-to-threats/investigate-and-respond-to-cases/investigate-issues/issue-investigation-actions/create-a-featured-field.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.