In tasks, you can bring order using filters—showing only the elements you need by the person responsible, task creator, status, or other parameters. This is especially useful when there are many tasks and you need to instantly find your own or review team progress.
Now there are even more possibilities thanks to the new Advanced tab in the Filters window. As before, you can add and remove fields, but additionally you can select a condition and set a value for each field. You can also control the filter logic by combining conditions using AND and OR, allowing you to build truly flexible queries.
Components of advanced filters
On the Advanced tab, a filter is built from individual “building blocks”—conditions and groups—which can be combined using the logic you need.
1. Logical operators: AND / OR
In Advanced Filters, the AND and OR logical operators are applied at every level of the filter builder. The operator at a given level determines how all elements at that level are combined: individual conditions (rows with fields) and/or groups of conditions.
Typically, there are three levels of nesting:
🟣 First level — Overall (top level)
This is the logic of the entire filter. It defines how all top-level elements are combined:
individual conditions (fields) added without a group;
groups of conditions.
🟣Second level — Logic within a group of conditions
When you add a Condition group, it has its own AND / OR operator. This operator determines how conditions and/or nested groups inside this group are combined.
🟣Third level — Logic within a nested group
If you create another Condition group inside a group, it will also have its own AND / OR operator and will combine elements at its own (nested) level.
Example of such a structure:
At the first level, the operator combines everything that appears at the top level (this can be a list of fields, a list of groups, or a combination of fields and groups).
At the second and third levels, operators are defined within condition groups and control how elements are combined within each specific group.
2. Condition, field, condition operator, and value
A condition is a single filter row where you configure a check for a specific field.
The foundation of every condition is the field you are filtering (selected from the list in the condition row). In Tasks, for example, this can be Person responsible, Task creator, Status, or other parameters—both default fields and any custom fields you have created.
Each condition includes a Condition operator—a dropdown list that defines how the field is evaluated. For example:
Equals
Not equal
Filled out
Not filled out
The available condition operators depend on the type of field being evaluated.
A value is the specific parameter you enter in the condition after selecting an operator, so the system knows what to compare the field against.
How the value is set depends on the selected condition operator:
If the operator requires a comparison (for example, Equals, Not equal), you must specify a value—that is, select or enter what the field should be compared to.
If the operator only checks for the presence of data (for example, Filled out, Not filled out), no value is required, because the system only verifies whether the field contains data.
The format of the value (a selectable list, single or multiple selection, or manual entry of text or numbers) also depends on the field for which the condition is being configured.
3. Condition group
A condition group is a separate block on the Advanced tab where you can combine multiple conditions (and, if needed, nested groups) to control the logic not for a single row, but for an entire set of rules.
Why you need a condition group
To combine multiple checks into a single “package” and apply shared logic to them.
To build complex filters with multiple levels—for example, when some conditions must be met together, while others work as alternatives.
What a group can contain
Multiple Condition rows (each consisting of: field → condition operator → value / no value).
One or more nested groups, if more advanced grouping is required.
Logic within a group
Each Condition group has its own AND / OR logic switch:
AND — all conditions and/or nested groups in the group must be met.
OR — at least one condition or nested group in the group must be met.
Example:
Group 1 (AND): Person responsible = Iryna AND Task creator = Alexandra
Group 2 (AND): Person responsible = Iryna AND Task creator = Valeriia
If OR is selected between these two groups at the top level, the results will include tasks that match either Group 1 or Group 2.
4. Removing a condition or a condition group from a filter
On the Advanced tab, you can remove unnecessary settings in two ways: delete an individual condition or delete an entire condition group.
🟣Remove a single condition
If you need to remove just one row from the filter (for example, the condition for the Person responsible field), click the trash icon to the right of that row.
The condition will be removed from the filter builder.
🟣Remove an entire condition group
If you need to remove a whole block (a group) along with all conditions inside it, click the trash icon in the upper-right corner of the group.
Specifics of сonfiguring сonditions by field type
On the Advanced tab, the set of available condition operators and the way values are entered depend on the field type. For example, text fields support operators like contains, while number fields allow you to define a range.
💡 For the Filled out and Not filled out operators, no value is entered.
Row, Text, Link, Address
Operators:
Equals — enter a value (exact match).
No equal — enter a value (excludes an exact match).
Contains — enter a value (checks whether the field contains the specified fragment).
Does not contain — enter a value (checks that the specified fragment is not present).
Starts with — enter a value (the field begins with the specified fragment).
Ends with — enter a value (the field ends with the specified fragment).
Filled out— no value is required.
Not filled out — no value is required.
If the field allows multiple values, the condition is checked against all values in the field.
Example:
If the filter is set to Address → Equals → New York, and the element’s Address field contains the values Chicago, Boston, New York, the element will be included in the results because at least one value matches the condition.
Integer, Number with fractional part
Operators:
Equals — enter a number (the value must exactly match the entered number).
Not equal — enter a number (the value must not match the entered number).
Greater than — enter a number (the value must be strictly greater than the entered number).
Less than — enter a number (the value must be strictly less than the entered number).
Greater than or equal to — enter a number (the value must be greater than or equal to the entered number).
Less than or equal to — enter a number (the value must be less than or equal to the entered number).
Range from … to … — enter two numbers:
From — the value must be greater than or equal to the specified “from” value.
To — the value must be less than or equal to the specified “to” value.
Filled out — no value is required.
Not filled out — no value is required.
If the field allows multiple values, the condition is checked against all values in the field.
Example:
If the filter is set to Coefficient → Equals → 3, and the element’s Coefficient field contains the values 1, 3, 5.2, the element will be included in the results because one of the values equals 3.
List, Tag
Operators:
Equals — select values from the list.
For a single-value field only one option can be selected. The match must be exact.
If you set Translation types → Equals → “Written”, the results will include only elements where the field contains only “Written.”
For a multi-value field multiple options can be selected. An exact set match is applied—the field must contain only the selected values, with no additional ones.
If you set Translation types → Equals → “Written”, the results will include only elements where the field contains only “Written.” Elements where the field contains “Written” and “Oral” will not be included. If you set Translation types → Equals → “Written” and “Oral”, the results will include only elements where the field contains exactly these two values and no others.
Not equal — select values from the list.
Works as the inverse of Equals, based on exact matching logic.
If you set Translation types → Not equal → “Written”, the results will include elements with any value except an exact match to “Written.”
Example for a multi-value field:
If you set Translation types → Not equal → “Written”, elements where the field contains only “Written” will be excluded.
Elements where the field contains “Written” and “Oral” will be included, because the set of values is not an exact match to “Written.”
Contains shows elements where the field contains all selected values. If multiple options are selected, they must all be present in the field at the same time (either alone or together with other values).
For a single-value field: This operator is not available.
For a multi-value field: Selecting multiple options returns results where all selected values are present.
Examples (multi-value field “Translation type”):
If the filter is set to Contains → “Written”, the results will include elements where the field contains: only “Written”, or “Written” together with other values (for example, “Written” and “Oral”).
If the filter is set to Contains → “Written” and “Oral”, the results will include elements where the field contains: “Written” and “Oral”, or “Written,” “Oral,” and additional values (for example, “Simultaneous”).
Does not contain is the inverse of Contains. Shows elements where the condition “contains all selected values” is not met.
For a single-value field: This operator is not available.
For a multi-value field: Results will include elements where none of the selected values are present, or only some of the selected values are present (but not all at the same time).
Example (multi-value field “Translation type”):
If the filter is set to Not contain → “Written” and “Oral”, the results will include elements where both values are not present together (for example, only “Written”, only “Oral”, or neither of them).
Contains any show elements where the field contains at least one of the selected values. When multiple options are selected, OR logic is applied.
For a single-value field: Selecting multiple options applies OR logic—elements with value option 1 or option 2, and so on, are included.
For a multi-value field: Selecting multiple options also applies OR logic—elements are included if they contain option 1, option 2, both, or any combination of them.
Examples (field “Translation type”):
Single-value field: If you select Contains any → “Written”, “Oral”, the results will include elements where the field value is either “Written” or “Oral.”
Multi-value field: If you select Contains any → “Written”, “Oral”, the results will include elements where the field contains “Written,” “Oral,” or both.
Contains none is the inverse of Contains any. Shows elements where the field contains none of the selected values.
Example (field “Translation type”):
If you select Contains none → “Written”, “Oral”, the results will include elements where the field contains neither “Written” nor “Oral.”
Filled out — No value selection is required.
Not filled out — No value selection is required.
User
Operators:
Equals — select a user.
For a single-value field: Select one user. An exact match is required.
The results will include tasks where the Participants field contains only Shakespeare.
Tasks where the participants are Shakespeare and Dickens will not be included.
For a multi-value field: Select multiple users. An exact set match is applied—the field must contain only the selected users.
If you set Participants → Equals → Shakespeare, the results will include records where the field contains only Shakespeare. Records with Shakespeare + Dickens will not be included. If you select Shakespeare and Dickens, the results will include only records where both users are present and no others.
Not equal — select a user.
For multi-value fields, this operator works using OR logic: not equal User 1 OR not equal User 2, etc.)
Tasks where the Participants field contains only Shakespeare will be excluded.
Tasks where the participants are Shakespeare and Dickens will be included, because this is no longer an exact match to "Shakespeare."
Contains shows elements where the field contains all selected users. They must be present in the field at the same time (either alone or together with other users).
For a single-value field: This operator is not available.
For a multi-value field: Selecting multiple users returns results where all selected users are present.
Examples (multi-value field, such as “Participants”):
If the filter is set to Contains → “Shakespeare”, the results will include elements where the field contains: only Shakespeare, or Shakespeare together with other users (for example, Shakespeare and Dickens).
If the filter is set to Contains → “Shakespeare” and “Dickens”, the results will include elements where the field contains: Shakespeare and Dickens, or Shakespeare, Dickens, and additional users.
Does not contain is the inverse of Contains. Shows elements where the condition “contains all selected users” is not met.
For a single-value field: This operator is not available.
For a multi-value field: Results will include elements where none of the selected users are present, or only some of the selected users are present (but not all at the same time).
Example (multi-value field):
If the filter is set to "Does not contain → “Shakespeare” and “Dickens”, the results will include elements where both users are not present together—for example, only Shakespeare(without Dickens), only Dickens, or neither of them.
Contains any shows elements where the field contains at least one of the selected users. When multiple users are selected, OR logic is applied.
For a single-value field: Selecting multiple users applies OR logic—elements where the field value is Shakespeare or Dickens, and so on, are included.
For a multi-value field: Selecting multiple users also applies OR logic—elements are included if they contain Shakespeare, Dickens, or both.
Examples:
Single-value field (for example, Person responsible): Contains any → “Shakespeare”, “Dickens” — results include elements where the person responsible is either Shakespeare or Dickens.
Multi-value field (for example, Participants): Contains any → “Shakespeare”, “Dickens” — results include elements where the participants include Shakespeare, Dickens, or both.
Contains none is the inverse of Contains any. Shows elements where the field contains none of the selected users.
Example (multi-value field): Contains none → “Shakespeare”, “Dickens” — the results will include elements where neither Shakespeare nor Dickens is present.
Filled out — No value selection is required.
Not filled out — No value selection is required.
Date
Operators:
Equals — select a date and time. The filter will show elements where the field value exactly matches the chosen date and time.
Example: Deadline → Equals → 12/31/2025 12:00 PM
Not equal — select a date and time. The filter will show elements where the field value does not match the chosen date and time.
Example: Deadline → Not equal → 12/31/2025 12:00 PM
Before — select a date and time. The filter will show elements where the field value is earlier than the chosen date and time.
Example: Deadline → Before → 01/01/2026 12:00 AM (shows everything before this date)
After — select a date and time. The filter will show elements where the field value is later than the chosen date and time.
Example: Deadline→ After → 01/01/2026 12:00 AM (shows everything after this date)
Filled — no value selection required. Shows elements where a date is present in the field.
Not filled — no value selection required. Shows elements where the date field is empty.
Quick date options
When selecting a date in the condition, you can use quick options instead of manually picking a day from the calendar:
Today / Tomorrow / Yesterday
Today — inserts the current date.
Tomorrow — inserts the next day.
Yesterday — inserts the previous day.
This week / This month / This year
This week — current calendar week.
This month — current calendar month.
This year — current calendar year.
Last week / Last month / Last year
Last week — previous calendar week.
Last month — previous calendar month.
Last year — previous calendar year.
Next week / Next month / Next year
Next week — next calendar week.
Next month — next calendar month.
Next year — next calendar year.
Range
Allows you to define a date interval:
Select a from date and a to date, and the filter will show elements whose date falls within this range.
Money
The Money field consists of two parts, and filtering works separately for each:
Value— filtering works the same as a Number field.
Currency — filtering works the same as a List field.
Phone, Email, Social networks
Operators are the same as for text fields:
Equals
Not equal
Contains
Does not contain
Starts with
Ends with
Filled out
Not filled out
Checkbox
A Checkbox is a field where you can either check or uncheck the box. In filters, it is treated as a value: Yes → checked, No → unchecked.
Operators:
Equals — shows elements where the checkbox matches the selected state.
Equals → Yes → shows elements with the checkbox checked.
Equals → No → shows elements with the checkbox unchecked.
Examples:
Urgent → Equals → Yes — shows all urgent tasks.
Needs review → Equals → No — shows tasks that do not require review.
Not equal — shows elements where the checkbox does not match the selected state.
Not equal → Yes → shows elements where the checkbox is not checked (i.e., No)
Not equal → No → shows elements where the checkbox is checked (i.e., Yes)
Examples:
Urgent → Not equal → Yes — shows tasks that are not marked urgent.
Needs review → Not equal → No — shows tasks marked as requiring review.
Filled out — the field has a value (Yes or No).
Not filled out — the field has no value.
Image, File
💡 At the moment, filtering for Image and File field types is not available on the Advanced tab.
Working with advanced filters
Advanced filters work the same way as Simple filters. They provide more flexibility for building conditions, while the overall interaction principles remain the same as in standard (basic) filters. That means you can still:
apply a configured filter and get a filtered list;
cancel changes or reset filtering;
save a set of conditions as a separate filter and later find it on the Saved tab;
apply, pin, or delete saved filters via the filter actions menu, as well as select them from the filter bar on the Tasks page.
🔍 To better understand the basic scenarios for working with filters and search (applying, saving, pinning, deleting), we recommend reading the article Filters and search in tasks.
If you have additional questions or you need to contact the support, send a request to this email [email protected]