Defect #37349

Chained custom field filter for User fields returns 500 internal server error when filtering after a float value

Added by Marius BALTEANU about 1 month ago. Updated about 1 month ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:Marius BALTEANU% Done:

0%

Category:Filters
Target version:4.2.8
Resolution:Fixed Affected version:4.2.7

Description

This was discovered during the investigations for #36940.

Steps to reproduce:

  1. Create a user custom field A of type float and check Used as a filter
  2. Create an issue custom field B with format User and check Used as a filter
  3. On the My account page set the custom value A for your own account to an arbitrary value
  4. 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.

Associated revisions

Revision 21684
Added by Marius BALTEANU about 1 month ago

Fix filter for chained User custom fields returns 500 internal server error when filtering after a float value (#37349).

Revision 21685
Added by Marius BALTEANU about 1 month ago

Revert undesired change (#37349).

Revision 21688
Added by Marius BALTEANU about 1 month ago

Merged r21684 and r21685 to 5.0-stable (#37349).

Revision 21689
Added by Marius BALTEANU about 1 month ago

Merged r21684 and r21685 to 4.2-stable (#37349).

History

#1 Updated by Marius BALTEANU about 1 month ago

  • Affected version changed from 4.2.6 to 4.2.7

#2 Updated by Marius BALTEANU about 1 month ago

  • Category changed from Issues filter to Filters

#3 Updated by Marius BALTEANU about 1 month ago

  • Status changed from New to Resolved
  • Resolution set to Fixed

#4 Updated by Marius BALTEANU about 1 month ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF