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

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) almost 12 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