プロジェクト

全般

プロフィール

Vote #70403

未完了

Ability to manage Role assignments by individual Group Member.

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

ステータス:
New
優先度:
通常
担当者:
-
カテゴリ:
Issues workflow_41
対象バージョン:
-
開始日:
2011/07/23
期日:
進捗率:

0%

予定工数:
category_id:
41
version_id:
0
issue_org_id:
8891
author_id:
5858
assigned_to_id:
0
comments:
6
status_id:
1
tracker_id:
2
plus1:
0
affected_version:
closed_on:
affected_version_id:
ステータス-->[New]

説明

Currently, assigning a Group to a Project and Role is an all-or-nothing proposition, as one can only assign an entire Group to a Project Role, and once assigned, individual Group members cannot be removed from that role.

We have groups for Developers, QA Analysts, BA's, etc., but these groups cannot be assigned to projects directly, because no project is worked on by ALL the developers or QA people and certainly not managed by ALL the PM's. The Group becomes useful mostly as a pick list to use when assigning users to projects.

Some method of adding and removing individual Group members from projects and roles is needed, and would greatly improve the usefulness of Groups.


journals

I think that "problem" should be solved by proper groups and not using groups a container for people of same role. In user mangament system like ldap you have organizational groups or project groups and if u use roles you would would have attribute on individual persons but not use groups for that.
Using groups to assign roles above project level doesn't have any more adavantages than working around some "strange" grouping behaviour.
--------------------------------------------------------------------------------
Agree with Terence.
--------------------------------------------------------------------------------
Using groups for people of the same role isn't proper? Not sure how else one would do it.. If you made a group for each unique combination of individuals in a given role, that would quickly grow to a unique group per project role, which is no better than simply managing individuals at the project level.

For example.. Assume 50 projects, 20 developers, 20 QA people, and each project has a unique combination of developers and QA people assigned to it at any one time. The proper use of groups is to create 100 groups?

--------------------------------------------------------------------------------
This limitation can be worked around by assigning the group to a role with limited privileges. You can then add and remove additional roles to specific individuals in the group.
--------------------------------------------------------------------------------

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

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


related_issues

relates,New,18424,can be in the project group management
relates,New,5542,Allow register users to add/remove themselves from a project

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

  • カテゴリIssues workflow_41 にセット

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

いいね!0
いいね!0