# \[Logic/UX/UI\] Filters - Multiselect "Contains" Operator Allows Only One Value

**URL:** <https://community.fibery.io/t/logic-ux-ui-filters-multiselect-contains-operator-allows-only-one-value/10418>\
**Category:** Bugs & Issues\
**Created:** [February 21, 2026, 3:48pm UTC](https://community.fibery.io/t/logic-ux-ui-filters-multiselect-contains-operator-allows-only-one-value/10418 "2026-02-21T15:48:38Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sev](https://avatars.discourse-cdn.com/v4/letter/s/90db22/32.png) [@Sev](https://community.fibery.io/u/Sev)\
**Post date:** [February 21, 2026, 3:48pm UTC](https://community.fibery.io/t/logic-ux-ui-filters-multiselect-contains-operator-allows-only-one-value/10418/1 "2026-02-21T15:48:38Z")

</div>

A **multiselect** field implies **multi-value semantics** i.e. that multiple selections are meaningful simultaneously. Therefore restricting it to a single value contradicts the presumably predominant user intent.

This is exactly what happens in the **contains** operator of **multiselect** field filters, as shown below in the second dropdown. For example, we cannot show entities tagged X AND Y in the second filter, whereas we can show entities tagged X OR Y in the first filter.

![Fibery-multiselect-filter-contains](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/0/0099e221f7da9b8a02646c84ab977f54c25ea9e9.gif)

While **contains any of** naturally supports multiple values and joins them with **OR** when applying the filter logic, **contains** operators for a **multiselect** (also named **contains all of** e.g. [at Hubspot](https://knowledge.hubspot.com/segments/determine-filter-criteria#object-and-activity-properties)) also support multiple values but join them with **AND**.

#### Current workaround

Currently to filter by a multiselect field that contains X AND Y AND Z, we need to create three filters.

#### Suggested Solution

Change **multiselect fields’ contains** filter value selector component from `singleValue` to `multiValue` and apply the **AND** logic when **contains** is used. Perhaps renaming to **contains all of** woudl be even more clear.

From what I have seen, this will be a non-breaking improvement, as current filters will continue to work, since the improved **contains/contains all of** that allows multiple values, **will still both semantically and logically make sense when one value is selected**.