Ability to manage Role assignments by individual Group Member.
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.
#1 Updated by Terence Mill about 11 years ago
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.
#3 Updated by William Baum about 11 years ago
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?