Chained custom field filter for User fields returns 500 internal server error when filtering after a float value
|Assignee:||Marius BALTEANU||% Done:|
This was discovered during the investigations for #36940.
Steps to reproduce:
- Create a user custom field A of type float and check Used as a filter
- Create an issue custom field B with format User and check Used as a filter
- On the My account page set the custom value A for your own account to an arbitrary value
- Filter the issue list by the filter B's A and use the value you set on the My account page
Observe that the page returns 500 error with the following error in logs:
Query::StatementInvalid: PG::UndefinedFunction: ERROR: operator does not exist: text >= numeric LINE 1: ...' AND custom_field_id=12 AND custom_values.value BETWEEN 32... ^ HINT: No operator matches the given name and argument types. You might need to add explicit type casts.
Fix filter for chained User custom fields returns 500 internal server error when filtering after a float value (#37349).