Defect #18894
Grouping of Boolean field: Both "No" and "blank" tickets are grouped in "none" groups
Status: | Closed | Start date: | ||
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | % Done: | 0% | ||
Category: | Custom fields | |||
Target version: | 2.6.2 | |||
Resolution: | Fixed | Affected version: | 2.5.0 |
Description
- 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
Associated revisions
Fixed that boolean custom field groups have same label for blank and false values (#18894).
History
#1
Updated by kaz k almost 5 years ago
- File 02_English_QueryResult_GroupedByBoolean(optional)_BothNoAndBlankAreGroupedUnder-none-.jpg added
Screen capture
Here is a screen capture of query-result grouped by boolean field. In the picture, Boolean1optional is a boolean filed without "required" specification. You could see 2 groups with "none" group label.
Notes on Label Texts
It is simple to reflect the values to the label texts, ie. Yes/No/null(or "blank").
Notes on translation
I am afraid translation texts may be affected when changing the label texts. For example, "none" is translated to "なし" in Japanese.
#2
Updated by Toshi MARUYAMA almost 5 years ago
- Status changed from New to Confirmed
#3
Updated by Toshi MARUYAMA almost 5 years ago
- Target version set to 2.6.2
#4
Updated by kaz k almost 5 years ago
Status changed from New to Confirmed
Target version set to 2.6.2
Thank you.
#5
Updated by Jean-Philippe Lang almost 5 years ago
- Subject changed from Grouping of Boolean field in Query: Both "No" and "blank" tickets are grouped in "none" groups. They should better to be distinguished. to Grouping of Boolean field: Both "No" and "blank" tickets are grouped in "none" groups
- Status changed from Confirmed to Resolved
- Assignee set to Jean-Philippe Lang
- Resolution set to Fixed
Fixed in r13921.
kaz k wrote:
Could it be changed the label of "none" for " (blank, or to say, not specified) " to "null", "No Value", or" (blank) " ?
I agree, would you fill a separate ticket for this? Thanks.
#6
Updated by kaz k almost 5 years ago
Jean-Philippe Lang wrote:
kaz k wrote:
Could it be changed the label of "none" for " (blank, or to say, not specified) " to "null", "No Value", or" (blank) " ?
I agree, would you fill a separate ticket for this? Thanks.
Per your request, I created a separate ticket, #18918.
Thank you for your quick response. I appreciate redmine team very much.
#7
Updated by Jean-Philippe Lang almost 5 years ago
- Status changed from Resolved to Closed