Defect #15854

Searchable checkbox always set to FALSE after updating Custom Field

Added by Wit Waw almost 9 years ago. Updated almost 9 years ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:


Category:Custom fields
Target version:-
Resolution: Affected version:2.4.2


It's possible however to set it using direct SQL statement ie.:

update custom_fields set searchable=1 where id=1;

Any further update to the Custom Field will clear this checkbox again.

After checking it up manually it works properly.

Redmine version 2.4.2.stable (from redmine-2.4.2.tar.gz)
Ruby version 1.8.7-p352 (2011-06-30) [x86_64-linux]
Rails version 3.2.16
Environment production
Database adapter Mysql2
MySQL 5.1.71


#1 Updated by Marvin Hohlfeld almost 9 years ago

Same "defect" here... however, this only happens on some field types like integer, float, date,...

It is a hard-coded restriction in the custom fields code, see also:

+1 for making integers searchable!

Also available in: Atom PDF