From: Patrick S. <sch...@in...> - 2007-10-27 08:37:23
|
Hi Victor, I am currently unsure if I get you right, so I need to ask further to clarify things. :) On Fri, Oct 26, 2007 at 10:51:22AM -0700, Victor Boctor wrote: > However, I am not as convinced that assigning an issue to multiple > users/groups adds value. In my mind, if an issue is to be assigned to > multiple users, then there is no accountability. In such case, we > should create child issues with the appropriate scopes and assign them > to the right resources. I'm not sure if I get you right. You say its bad to assign issues to several people looseley but you instead think that defining a group of those members and then assigning the issues to the group would be more suffice? If that group is just a logical division then I agree. That would probably be most valueable. An example: At my company I am working for the Operations Division (that is the Network Administrators). We track ToDo and project items in Mantis company wide. There are often tasks that have to be solved by us in team work and I want to see that in the statistics. Currently I can't because someone needs to take over credit for what has been done. I wasn't sure if you meant to do this via group _accounts_, so that one would not login with his own account but with a group account, which wouldn't suffice ime. So what would we need for this group thing? - a new table for groups - a new table to define group memberships (this enables to let several people be in several groups) - management interface for user-group-memberships - make groups selectable in the interface so one can design tasks to them - Send emails to all members of a group instead of users - Handle groups in stats pages etc. as they were users (because it makes no difference weither an user took two weeks to complete a task or a group). I would suggest to implement this as a first step (because it is eventually the most needed part of functionality), then later some features could be added to that: - Access Control: Are all group members able to do the same things, restrictions? - Access Control: Let one be able to define a group operator who is able to add/remove users from a group (for now it would be suffice to let the usual admin do that) More? Regards, Patrick |