Workflow builder - text / links fields miss the option "IS" match in UI

[ClaireGz]

Bug Description

When filtering on a text / links field (ex: company domain), the UI only show filters like "contains" or "empty/not empty" while i want to do an exact match. And by the API, I can set this same condition "IS" (exact match), but not in the UI

Another subissue of this: It's impossible even with the API to match exact value among any of the value of an array field.
Ex for company domain, I want to search records where any of the domain values is exactly domain.com
It's not possible: I can only match primary domain is exactly domain.com, but since secondary ones are arrays, it can't do an exact match.
I had to do a workaround with a code that does it instead.

Expected behavior

Be able to set the IS filter from the UI

[twenty-eng-sync[bot]]

Kind: Probably a real bug. The workflow filter UI does not offer the IS exact-match operand for text and links fields, although the workflow API accepts it.
Severity: MEDIUM — exact matching is unavailable in the builder, but the API provides a workaround.
Root-cause hypothesis (medium confidence): packages/twenty-front/src/modules/workflow/workflow-steps/filters/components/WorkflowStepFilterOperandSelect.tsx gets its options from filters/utils/getStepFilterOperands.ts; that utility maps TEXT and LINKS to the shared FILTER_OPERANDS_MAP.TEXT, whose resulting UI options omit IS despite workflow support.
The report is missing the affected Twenty version and the exact workflow trigger/action where the filter was configured.

[sonarly[bot]]

🟡 Sonarly Analysis — Medium Severity

Missing exact-match operand for workflow text and link filters

The workflow builder omits the IS operand for text and link fields, preventing exact-match conditions from being configured in the UI. The workflow executor also lacks IS handling for these field types, so this is a capability mismatch rather than a dropdown-only defect.

Root Cause

The workflow operand selector derives its options from getStepFilterOperands. For TEXT, EMAILS, FULL_NAME, ADDRESS, LINKS, and PHONES, that function returns FILTER_OPERANDS_MAP.TEXT:

case 'TEXT':
case 'EMAILS':
case 'FULL_NAME':
case 'ADDRESS':
case 'LINKS':
case 'PHONES':
  return FILTER_OPERANDS_MAP.TEXT;

FILTER_OPERANDS_MAP.TEXT contains only CONTAINS, DOES_NOT_CONTAIN, IS_EMPTY, and IS_NOT_EMPTY; it does not contain IS. The selector maps that returned array directly into its dropdown options, so there is no later rendering or metadata condition that could expose the missing option. [ref:workflow-operand-map]

This is also a backend capability gap. Workflow execution routes TEXT and LINKS through evaluateTextAndArrayFilter, whose switch handles only CONTAINS, DOES_NOT_CONTAIN, IS_EMPTY, and IS_NOT_EMPTY. An IS operand reaches the default branch and raises Operand IS not supported for this filter type. [ref:workflow-evaluator]

The workflow schema accepts every value in ViewFilterOperand, including IS, without validating compatibility against the selected field type. Therefore a caller can persist or submit a structurally valid IS operand even though the UI does not offer it and the workflow executor cannot evaluate it. This explains the reported API/UI mismatch: enum acceptance is broader than actual workflow execution support. [ref:step-filter-schema]

The triggering cause is not a traffic, data, or infrastructure event. Git history shows the text operand allowlist already excluded IS in the workflow filter implementation added with the If/Else filter UI on 2026-01-01. Commit 068d365731a337f7500aa8010c5295fb1a371866 later added the shared FILTER_OPERANDS_MAP and rewired getStepFilterOperands to use it, but the prior workflow map had the same exclusion. The exact reason the issue was reported at this time is unknown; no deployment timeline, product analytics, affected-entity data, or error telemetry was provided. [ref:workflow-history] [ref:shared-map-refactor]

Blame commit: 068d3657 by ehconitin — feat(sdk): error on incompatible view filter operand at sync time (#20763)

Suggested Fix

Added an IS operand to workflow text-like filters, including TEXT and LINKS, while preserving the existing shared FILTER_OPERANDS_MAP behavior for non-workflow record filters. Added strict equality evaluation for IS in the workflow text/array evaluator and covered matching and non-matching TEXT and LINKS cases.

---

Analyzed by Sonarly · View full analysis

[thomtrp]

This is actually by design, can be discussed