[Custom Fields] Filter by text and number types
Proposal
Support filtering by text and number types anywhere custom fields filtering is supported.
Proposed UX
- Field selection: User selects field token using standard filter behavior (fields appear using field type icon + field name)
- Operator selection:
- For text fields, options are "contains"
~=(or just~, only slight preference for include equal sign), "does not contain"!=, "is exactly"=, "is set"= *, "is not set"!= * - For number field, options are "is exactly"
=, "greater than">, "less than"<, "is set"= *, "is not set"!= * - Showing the operator for Is set and Is not set is optional assuming they utilize standard operators + wildcards, as noted below
- "Is set" applies
=plus a wildcard, such as*, as the value which is automatically closed as a token (i.e. user does not have an input step when selecting "exists") - "Is not set" applies
!=and*
- For text fields, options are "contains"
- Value entry works similar to text search: no autocomplete is shown, user enters text in the input and on "enter" the token is closed. The search does not apply on token close (existing filtered search behavior).
Edited by Nick Leonard