Actions
Defect #37349
closedChained custom field filter for User fields returns 500 internal server error when filtering after a float value
Start date:
Due date:
% Done:
0%
Estimated time:
Resolution:
Fixed
Affected version:
Description
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.
Updated by Marius BĂLTEANU over 2 years ago
- Affected version changed from 4.2.6 to 4.2.7
Updated by Marius BĂLTEANU over 2 years ago
- Category changed from Issues filter to Filters
Updated by Marius BĂLTEANU over 2 years ago
- Status changed from New to Resolved
- Resolution set to Fixed
Updated by Marius BĂLTEANU over 2 years ago
- Status changed from Resolved to Closed
Actions