> 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-cloud-runtime-security/cases-and-issues/investigation-and-response/automation/playbooks/build-your-playbook/customize-your-playbook/update-issue-fields-with-playbook-tasks.md).

# Update issue fields with playbook tasks

Update issue fields using tasks in a playbook.

During the investigation, you can set and update issue fields using the setIssue script in a playbook task.

{% hint style="warning" %}

### Important

While the setIssue script includes most system fields, it does not support updating the **Assignee** field. If your playbook needs to assign an owner to an issue, replace the task executing the `setIssue` script with an integration command task using the `core-update-issue` command (found under the Cortex Core - Platform integration).You initially define issue fields after the planning stage, with mapping and classification for how the issues will be ingested from third-party integrations into Cortex Cloud.
{% endhint %}

* Use the scroll bar to see all available fields for the setIssue script.
* The `name` field has a limit of 600 characters. If there are more than 600 characters, you can shorten the `name` field to under 600 characters and then include the full information in a long text field such as the `description` field.

For more information, see [Update issue fields](/cortex-cloud-runtime-security/cases-and-issues/investigation-and-response/investigate-issues/issue-investigation-actions/update-issue-fields.md)

<br>


---

# 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-cloud-runtime-security/cases-and-issues/investigation-and-response/automation/playbooks/build-your-playbook/customize-your-playbook/update-issue-fields-with-playbook-tasks.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.