Begin of the insertion**As a** developer / consumerEnd of the insertion Begin of the deletion **As** a \[enter roleEnd of the deletion of Begin of the insertion`UserQuery` (HAL+JSON API, internal services such as the upcoming Resource Allocation feature, and any UI built on top of `PersistedQuery`)End of the insertion Begin of the deletion user\]End of the deletion
**I want to** Begin of the insertionfilter, sort and select user queries by `UserCustomField` valuesEnd of the insertion Begin of the deletion \[enter objective\]End of the deletion
**so that** Begin of the insertionI can express selections like "all active developers, sorted by birthday, with the Job title column visible" using the same primitives we already have for projects and work packages.End of the insertion Begin of the deletion \[enter desired result\]End of the deletion

Begin of the insertion## Acceptance criteriaEnd of the insertion Begin of the deletion **Acceptance criteria**End of the deletion

* Begin of the insertion[x] `UserQuery` accepts a `cf_<id>` filter for any visible `UserCustomField` (string, text, int, float, date, bool, list, multi-list).
End of the insertion Begin of the deletion <br>


**Technical notes**

End of the deletion * Begin of the insertion[x] All operators supported by the corresponding shared CF strategy workEnd of the insertion Begin of the deletion <br>


**PermissionsEnd of the deletion and Begin of the insertionproduce the expected SQL:
End of the insertion Begin of the deletion visibility considerations**

End of the deletion * Begin of the insertion`=`, `!`, `*`, `!*` for list / list-optional

* `=`, `!`, `~`, `!~`, `*`, `!*` for string/text

* `<>d`, `=d`, `>t-`, `<t-`, `t`, `w` and friends for date — including the &quot;greater than or equal&quot; use case via `<>d` with an open upper bound (`["YYYY-MM-DD", ""]`)

* the standard numeric operators

* [x] `UserQuery` accepts a `cf_<id>` order for any visible `UserCustomField` whose formatEnd of the insertion Begin of the deletion _To whomEnd of the deletion is Begin of the insertionsortable (everything except `text`):
End of the insertion Begin of the deletion this feature visible?_

End of the deletion * Begin of the insertionasc and desc both produce stable, expected orderings

* NULL values land at the natural end (NULLS FIRST on asc, NULLS LAST on desc)

* text CFs are rejected as non-sortable (`available? == false`, `query.valid? == false`)

* [x] `UserQuery` accepts a `cf_<id>` select for any visible `UserCustomField`. `Queries::Users::Selects::CustomField.all_available` enumerates one select per visible CF, and each select&#39;s `caption`End of the insertion Begin of the deletion _WhenEnd of the deletion is Begin of the insertionthe CF&#39;s `name`.
End of the insertion Begin of the deletion it not visible?_


**Translation considerations**

End of the deletion * Begin of the insertion[x] CF filters can be combined with the existing `name`, `status`, `group`, `login`, `blocked` filtersEnd of the insertion Begin of the deletion _Key termsEnd of the deletion and Begin of the insertionwith each other under AND semantics.
* [x] A `UserQuery` (which is a `PersistedQuery`) round-trips a CF filter, CF order and CF select through serialization. The on-disk JSONB shape for filters is `{ "attribute": "cf_<id>", "operator": "=", "values": ["<option_id>"] }`. Reloading reconstructs working filter/order/select objects that produceEnd of the insertion Begin of the deletion phrases inEnd of the deletion the Begin of the insertionsame results.
* [x] If the referenced custom field is deleted, the deserializer degrades gracefully:
* filters become `NotExistingFilter` and the query reports `valid? == false`

* orders become a `NotExisting`\-style order and the query reports `valid? == false`

* selects become unavailable

* nothing raises

* [x] Existing `ProjectQuery` and `WorkPackageQuery` CF filtering / sorting / selecting behaviour is unchanged.
* [x] `Queries::Register.{filters,orders,selects}[UserQuery]` includes the three new classes.

##

##

##

###

## OutEnd of the insertion Begin of the deletion key languages_&nbsp;


**OutEnd of the deletion of Begin of the insertionscopeEnd of the insertion Begin of the deletion scope**End of the deletion

* Begin of the insertion**Grouping** `**UserQuery**` **by a CF value** — only filter / order / select are added here; `group_by` for users is not introduced.

* **UI work** — no changesEnd of the insertion Begin of the deletion <br>


_Set the_ **To be informed/consulted teams** _fieldEnd of the deletion to Begin of the deletion include all teams necessary to be informed ofEnd of the deletion the Begin of the insertionuser administration list, user picker or any frontend filter / column / sort control. Hooking the new primitives into a UI is a follow-up.

* **API exposure** beyond what `UserQuery` already provides via the existing serialization path.

* **Filtering for Group or PlaceholderUser CFs.** `GroupCustomField` / placeholder-user CFs follow a similar pattern and would each need their own `CustomFieldContext` + filter + order + select.

* **Backfilling** or migrating existing persisted queries — there are none using `cf_<id>` for users today.End of the insertion Begin of the deletion changes._End of the deletion