Before this update, filters were limited to linear constraints with variables "and" (all filters must match) and "or" (at least one filter must match). Now we can do something like this ...

Use Case: Useful mostly for pipelines and priority sorting, a nested filter can be used to split up pipelines by particular priorities, status, and due dates for every member assigned to a long list of tasks. In the following example, a writing department with 6 writers split into 3 groups of 2 are assigned to a list of tasks labeled with status (on deck, writing, reviewing, completed), priority (high, medium, low), and due date.

• A department pipeline will show all tasks within the next week that are NOT published AND are of high and medium priority.

In addition, separate views will be constructed to show pipelines for each group of 2 writers within the next week AND of high and medium priority AND tasks that are not published.

There will be a separate view for low priority tasks.

There’s another view for published tasks within the past week AND the next week.

And lastly, a priority map of tasks in the next week that are NOT published.

View Example In Notion