I want to create a task filter with a particular variable. Firstly I want to know which version of camunda 8 supports this and secondly how this can be done?
Hi @anmolrane1989 ,
You can filter tasks by variables using the Tasklist REST API. Please check this documentation:
Returns the list of tasks that satisfy search request params. If an empty body is provided, all tasks are returned. Only one of `[searchAfter, searchAfterOrEqual, searchBefore, searchBeforeOrEqual]` search options must be present in request.
If you’d like to create a filter in the UI , then unfortunately, it’s not yet possible.
opened 11:01AM - 14 Feb 24 UTC
component:tasklist
public
designRequired:completed
target:8.5
docsRequired:simple
## Value Proposition Statement 🚀
Work on tasks that matter by utilizing flexi… ble filters\.
## User Problem 🤦
When users can't filter their task queues by relevant attribute values, they struggle to manage their tasks efficiently as they are overwhelmed by a long list of items\.
- Users struggle to discern which tasks require immediate attention \(are urgent\) and which can be deferred, based on a relevant work domain \(e\.g\. a specific customer or order\)
- This results in a longer time to execute tasks, accumulating in significantly longer process execution times\.
- It increases stress in task workers, resulting in a low employee experience\.
## User Stories 🧑🚀
As a task user, when browsing my tasks, I can specify a custom filter to limit the result items in the queue and find exactly what I need\.
- I can filter by
- process name \(drodpown\),
- task name \(free text\),
- tenant \(dropdown\),
- candidate groups \(free text\),
- assignee \(free text\),
- candidate users \(free text\)\.
- I can filter by key\-value pairs of
- variables and their values\.
- I can filter by a date range for
- due date,
- follow\-up date\.
<p></p>
\(Stretch\) I expect the current filter to be stored \(in locale storage\), so when I return to Tasklist or to the "custom filter" option, I still see it\.
<img width="612" alt="image" src="https://github.com/camunda/product-hub/assets/143816833/514fd76e-4734-49d2-8f36-c912d0d5ae15">
## Implementation 👷
<p></p>
We will build these filters based on the existing query interface\. After that, we already prepare for support for complex task queries using a mock interface \(covered in a separate epic\)\.
#### Limitations
- As the API currently provides an eq operator only, we can render only such filter options\.
- Most filters will require free text input in this iteration\. In a future iteration, we can invest into variable and value discovery \(to autopopulate selectable values, groups, task names\.\.\.\)\.
#### Out of scope
- This epic does not cover additional operators
- That is covered in Complex Task Queries
- Not covering persistence \(other then locale storage\) and management of filters
- Covered in Persistable Task Filtersw based on the existing query interface, or wait for complex task queries?
<sup>:robot: This issue is automatically synced from: [source](https://github.com/camunda/product-hub/issues/2087)</sup>
1 Like