> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/tutorials/guides/how-to-use-tasks/how-to-filter-tasks.md).
# How to filter tasks
This short tutorial goes through filtering tasks.
### Filtering tasks in the overview
Inside the Tasks overview, there are pre-made filters ready, allowing users to quickly access specific task lists without the need to set up manual filters each time.
You can also use column headers in the task overview table to define any specific filter values.
{% hint style="info" %}
**Tip** To read about how to search more effectively, read here: [Search help](/reference/pim/search/search-help.md)
{% endhint %}
The tasks overview page where the pre-made filters are placed.
### Filtering tasks in the side menu
In the side menu, you can filter tasks by 'Assigned to me' or 'Created by me'. Inside each tab you can also choose between 'Open tasks' or 'All tasks'. For additional filtering options, please refer to the Tasks overview.
The tasks side-menu and its filters.
---
# 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.struct.com/tutorials/guides/how-to-use-tasks/how-to-filter-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 `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.
