Actions
Defect #15854
closedSearchable checkbox always set to FALSE after updating Custom Field
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Custom fields
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Resolution:
Fixed
Affected version:
Description
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.
Environment:
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
Updated by Marvin Hohlfeld almost 11 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:
http://www.redmine.org/boards/1/topics/39406
+1 for making integers searchable!
Updated by Go MAEDA almost 2 years ago
- Status changed from New to Closed
- Resolution set to Fixed
Closing as a duplicate of #19093.
Actions