Actions
Defect #18894
closedGrouping of Boolean field: Both "No" and "blank" tickets are grouped in "none" groups
Start date:
Due date:
% Done:
0%
Estimated time:
Resolution:
Fixed
Affected version:
Description
Boolean custom field can have three values; "Yes", "No" and " (blank, or to say, not specified) " if the filed is not specified as "required".
- Ref.
- Issue #17003-6
- Wiki ""Boolean: checkbox (enabled/disabled) or radio buttons (null/yes/no) " in RedmineCustomFields
I think it is OK.
But I found that both "No" and " (blank, or to say, not specified) " are grouped under same name (label) of "none" collapse/expand indicator lines when I specified "Group results by" the boolean field which is not defined as "required".
The tickets are grouped in 2 groups and it is right I think.
But both groups have "none" indicated in collapse/expand indicator line. It is not a good idea, I think.
Boolean field which is not set as "required" contains 3 values, "Yes", "No" and " (blank, or to say, not specified) ", so it is better to be grouped in different labels.
Could it be changed the label of "none" for " (blank, or to say, not specified) " to "null", "No Value", or" (blank) " ?
Kind regards,
- Reported version
Redmine 2.5.0.stable. Details are as follows. - Test redmine (Windows7)
Environment: Redmine version 2.5.0.stable Ruby version 1.9.3-p231 (2012-05-25) [i386-mingw32] Rails version 3.2.17 Environment production Database adapter Mysql2
- Production redmine (Linux)
Environment: Redmine version 2.5.0.stable Ruby version 1.9.3-p484 (2013-11-22) [x86_64-linux] Rails version 3.2.17 Environment production Database adapter PostgreSQL
Files
Actions