Project

General

Profile

Actions

Defect #37349

closed

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

Added by Marius BĂLTEANU over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Category:
Filters
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed
Affected version:

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.
Actions #1

Updated by Marius BĂLTEANU over 2 years ago

  • Affected version changed from 4.2.6 to 4.2.7
Actions #2

Updated by Marius BĂLTEANU over 2 years ago

  • Category changed from Issues filter to Filters
Actions #3

Updated by Marius BĂLTEANU over 2 years ago

  • Status changed from New to Resolved
  • Resolution set to Fixed
Actions #4

Updated by Marius BĂLTEANU over 2 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF