Defect #13006: Filter "Assignee's group" doesn't work with group assignments - Redmine

Custom queries

Documentation issues
Open defects
Open features
Patch queue
Plugin issues
Translation patches

Actions

Copy link

Defect #13006

closed

Filter "Assignee's group" doesn't work with group assignments

Added by Jan Niggemann (redmine.org team member) over 11 years ago. Updated about 11 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Jean-Philippe Lang

Category:

Issues

Target version:

2.3.0

Start date:

Due date:

% Done:

Estimated time:

Resolution:

Fixed

Affected version:

Description

Reproduce

Configure group assignments
Assign issue to a group XYZ
List issues, set filter "Assignee's group" is "XYZ"

Output: No data to display

Expected output: Issues assigned to users belonging to group "XYZ" as well as issues assigned to group XYZ itself

Related issues

Related to Redmine - Defect #9132: Filtering by "Assignee's Group" doesn't show issues assigned to the group

Closed

2011-08-26

Actions

Related to Redmine - Feature #7867: Author group filtering

Reopened

2011-03-15

Actions

Related to Redmine - Defect #13758: Issue Filtering 'Assignee = <<me>>' shows group issues, but 'Assignee = Bob' does not

New

Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Jean-Philippe Lang over 11 years ago

Category set to Issues
Status changed from New to Resolved
Assignee set to Jean-Philippe Lang
Target version set to 2.2.3
Resolution set to Fixed

Fixed in r11285.

Actions

Copy link

Updated by Jan Niggemann (redmine.org team member) over 11 years ago

Status changed from Resolved to Closed

tested in 11289, fixed, closing
thank you!

Actions

Copy link

Updated by Jean-Philippe Lang over 11 years ago

Status changed from Closed to Resolved

Thanks for the feedback. FYI: I'm keeping it open until it's merged into the 2.2-stable branch.

Actions

Copy link

Updated by Toshi MARUYAMA about 11 years ago

Is this issue duplicate with #9132?

Actions

Copy link

Updated by Jan Niggemann (redmine.org team member) about 11 years ago

Reading #9132 I'd say: Yes.

Actions

Copy link

Updated by Toshi MARUYAMA about 11 years ago

I think Redmine 2.2.2 behavior is designed behavior implemented by #5869 1.1.0.
"Assign issues to groups" is implemented by #2964 1.3.0.
As described note-5 of #9132,
should we add new "Author group filtering" (#7867) instead of this issue r11285 ?

Actions

Copy link

Updated by Jan Niggemann (redmine.org team member) about 11 years ago

I thought of groups not only for privilege management, I also imagined being able to use them as support queues, i.e. a business can have groups like

Groupware
Windows
Hardware (Printers, PCs, Laptops)
...

I imagined a workflow like this:

Callcenter agent assigns issue to one of the groups
Group supervisor assigns issue to supporter (or a supporter assigns issue to himself)
supporter resolves issue

It truly is arguable if 2.2.2 already exposed the desired behavior before, or only after r11285...

Some thoughts:
In the broader picture, I'm afraid that we might scare off people with too many options, filters and such. While perfect for redmine-experts, new users can get confused with too many options and turn away.

Perhaps it'd be better the functionality stayed like before r11285 and for my idea of issue queues, we recommend people create a custom field for the group assignment? After all, if a group and no particular user is assigned, there's no assignee. A supervisor would then be able to filter "assignee = none" AND "custom_group=Hardware"...

Actions

Copy link