プロジェクト

全般

プロフィール

Vote #73249

完了

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

Admin Redmine さんが約4年前に追加. 約4年前に更新.

ステータス:
Closed
優先度:
通常
担当者:
-
カテゴリ:
Issues_2
対象バージョン:
開始日:
2022/05/09
期日:
進捗率:

0%

予定工数:
category_id:
2
version_id:
60
issue_org_id:
13006
author_id:
55460
assigned_to_id:
1
comments:
10
status_id:
5
tracker_id:
1
plus1:
0
affected_version:
closed_on:
affected_version_id:
ステータス-->[Closed]

説明

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


journals

Fixed in r11285.
--------------------------------------------------------------------------------
tested in 11289, fixed, closing
thank you!
--------------------------------------------------------------------------------
Thanks for the feedback. FYI: I'm keeping it open until it's merged into the 2.2-stable branch.
--------------------------------------------------------------------------------
Is this issue duplicate with #9132?
--------------------------------------------------------------------------------
Reading #9132 I'd say: Yes.
--------------------------------------------------------------------------------
I think Redmine version:2.2.2 behavior is designed behavior implemented by #5869 version:1.1.0.
"Assign issues to groups" is implemented by #2964 version:1.3.0.
As described "note-5":http://www.redmine.org/issues/9132#note-5 of #9132,
should we add new "Author group filtering" (#7867) instead of this issue r11285 ?
--------------------------------------------------------------------------------
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"...
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Filter behaviour changed in r11285.
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------


related_issues

relates,Closed,9132,Filtering by "Assignee's Group" doesn't show issues assigned to the group
relates,Reopened,7867,Author group filtering
relates,New,13758,Issue Filtering 'Assignee = <<me>>' shows group issues, but 'Assignee = Bob' does not

Admin Redmine さんが約4年前に更新

  • カテゴリIssues_2 にセット
  • 対象バージョン2.3.0_60 にセット

他の形式にエクスポート: Atom PDF

いいね!0
いいね!0