Project

General

Profile

Actions
Copy link

Defect #18896

closed

Grouping of Boolean field in Query: group not displayed for "No" value if the group is in first position

Added by kaz k almost 10 years ago. Updated almost 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Jean-Philippe Lang
Category:
Custom fields
Target version:
2.6.2
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed
Affected version:
2.5.0

Description

When I submit the query with "Group results by" the boolean field which is defined as "required" , collapse/expand indicator line for "No" is not displayed.
  • Tickets are distinguished into 2 groups, one for "No" and the other for "Yes". OK.
  • But collapse/expand indicator line for "No" is not displayed. It should be displayed, I think.
    • On the other hand, collapse/expand indicator line for "Yes" is displayed. OK.

I'd appreciate if this issue is picked up and will be examined/fixed.

Kind regards,

  • Reported version
    Redmine 2.5.0.stable.
    Details are as follows.
    1. 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
    2. 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

Note: This phenomena does not happen with a boolean field which is not defined as "required". In this case, 3 collapse/expand indicator lines are displayed (with misleading labels ( see #18894 ) when this ticket is created).

Files

Download all files
03_English_QueryResult_GroupedByBoolean(required)_NoIsGroupedWithoutCollapse-Expand-Indicatorline.jpg (105 KB) 03_English_QueryResult_GroupedByBoolean(required)_NoIsGroupedWithoutCollapse-Expand-Indicatorline.jpg screen capture of query-result grouped by boolean field (specified as equired) kaz k, 2015-01-19 08:33
2.6.1.png (34.9 KB) 2.6.1.png Toshi MARUYAMA, 2015-01-19 08:47
2.6.1-confirmed.png (16.9 KB) 2.6.1-confirmed.png Toshi MARUYAMA, 2015-01-19 10:50
Actions
Copy link
 #1

Updated by kaz k almost 10 years ago

Screen capture
Here is a screen capture of query-result grouped by boolean field.
In the picture, Boolean2required is a boolean filed with "required" specification.
You could see 2 groups of tickets, one for "No" and the other is "Yes".
But "No" tickets do not have collapse/expand indicator line of "No" at the top of the tickets. "Yes" tickets have one for "Yes".

Actions
Copy link
 #2

Updated by Toshi MARUYAMA almost 10 years ago

I cannot reproduce on 2.6.1.

Actions
Copy link
 #3

Updated by kaz k almost 10 years ago

Toshi MARUYAMA wrote:

I cannot reproduce on 2.6.1.

Thank you for your quick reply.

According to the picture attached, it seems the boolean field has an attribute of "Not REQUIRED" because the list is grouped in 3 groups, 2 of "none" and 1 of "Yes".
As I write in the description, the phenomena happens if the boolean fields is defined as "Required", ie. Values are only 2 variations of "Yes" and "No".

Actions
Copy link
 #4

Updated by Toshi MARUYAMA almost 10 years ago

Confirmed.

Actions
Copy link
 #5

Updated by kaz k almost 10 years ago

Toshi MARUYAMA wrote:

Confirmed.

Thank you.

Actions
Copy link
 #6

Updated by Jean-Philippe Lang almost 10 years ago

  • Subject changed from Grouping of Boolean field in Query: collapse/expand indicator line is not displayed for "No" value. to Grouping of Boolean field in Query: group not displayed for "No" value if the group is in first position
  • Status changed from Confirmed to Resolved
  • Assignee set to Jean-Philippe Lang
  • Resolution set to Fixed

Fixed in r13922, thanks for pointing this out.

Actions
Copy link
 #7

Updated by Jean-Philippe Lang almost 10 years ago

  • Status changed from Resolved to Closed
Actions
Copy link

Also available in: Atom PDF