> 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/xsoar-6-administrator-guide/6.15/investigate-and-respond-to-threats/day-to-day-tasks-in-cortex-xsoar/incident-management/incident-tasks.md).
# Incident Tasks
Create and complete Cortex XSOAR 6.15 playbook and to-do tasks during investigations.
Incident tasks are tasks for users to complete as part of an investigation, which are split according to the following:
* **Playbook Tasks**: you can view, assign an owner, complete, and set a due date for playbook tasks that require attention.
* **To-Do Tasks**: create tasks for users to complete as part of an investigation, and which are not attached to the incident's playbook. A playbook can finish running and an incident can be closed even if the incident contains open To-Do tasks.
You can create a To-Do Task directly from the incident Case (incident) info tab or in the To-Do Task section.
Alternatively, you can create To-Do tasks from the command line.
### **Create a To-Do Task**
You can create To-Do tasks directly in the incident from either the Case (Incident) Info tab or the **Incident Tasks** window. You can also create To-Do Tasks using the command line.
1. From the incident, click 
and then click **Incident Task**.
2. In the **Incident Tasks** window, click the **To-Do Tasks** tab.
You can also add To-Do Tasks from the Case (Incident) Info tab if you have [customized](/xsoar-6-administrator-guide/6.15/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/incidents/incident-customization.md) the incident to include To-Do tasks.
3. Click **Add a task**.
4. Add the **Task Details** as required:
| Parameter | Description |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| Task Name | A meaningful name for the task (mandatory). |
| Task Description | A meaningful description for the task that provides sufficient information for the assignee to complete the task. |
| Assignee | The user to assign to the task. You can only assign a single user per task. |
| Set due date | The due date for the task. If the task is not completed by this date, it is marked as overdue but is not a roadblock for the investigation. |
| Tag the result with | Tags to apply to the To-Do task. |
5. Click **Save**.
If you have customized the incident, you can see the **To Do Tasks** from the Case (Incident) Info tab.
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.15/investigate-and-respond-to-threats/day-to-day-tasks-in-cortex-xsoar/incident-management/incident-tasks.md?ask=&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 `build a script that syncs our docs to a CMS` 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.