> For the complete documentation index, see [llms.txt](https://docs.bluestorm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluestorm.io/dashboards/tasks/task-details.md).

# Task Details

The purpose of a task is to describe you need to do, when you need to complete the task by, and give you the possibility to record information about the task.

* **Task status.** This summarizes the current status of the task, when it is due, who it is assigned to, and which app this task relates to.
* **Task instructions.** This describes how to perform the task.
* **Comments.** Use this to record information about the execution of the task. This is a rich text editor and it is possible to paste screenshots or other images.
* **Attachments.** Use this to store files that contain information about the execution of the task.

When you have completed the task click on 'complete task' to mark the task as completed. Once you have completed a task you will no longer receive notifications that it is due (or overdue).

{% hint style="info" %}
Tasks can only be completed by the people they have been assigned to, or by the person that assigned the task.
{% 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://docs.bluestorm.io/dashboards/tasks/task-details.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.