> 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/overview/tutorials/tasks/work-with-assigned-tasks.md).

# Work with assigned tasks

Use this tutorial to manage the tasks that were assigned to you.

### Before you start

* You need access to the app related to the task.
* The task must already be assigned.

{% stepper %}
{% step %}

### Open your task list

Go to [Dashboards → Tasks](/dashboards/tasks.md).

Filter the list to find your open tasks.
{% endstep %}

{% step %}

### Review the task details

Open the task.

Read the instructions, due date, and assignee details.

If the task includes sub-tasks, complete them in order.
{% endstep %}

{% step %}

### Update progress

Add comments or attachments when they help the reviewer.

Use task updates to document what you completed.
{% endstep %}

{% step %}

### Complete the task

Mark the task complete when all required work is done.

If the task blocks a pipeline, the release can continue after completion.
{% endstep %}
{% endstepper %}

### Next steps

* [Create a release](/overview/tutorials/releases/create-a-release.md)
* [Review policy compliance](/overview/tutorials/policies/review-policy-compliance.md)
* [Review governance readiness](/overview/tutorials/insights/review-governance-readiness.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://docs.bluestorm.io/overview/tutorials/tasks/work-with-assigned-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.