|
We have the same requirement. An issue may be created that requires work by an external group. The ability to assign to a group. By Notifying the assignee on assignment, an email would then be sent to the entire group, of which a group member could log in, and assign to themself for further work.
Thanks. Oh yeah, we're using JIRA 3.4.1 Build 107
Tobias,
If we implemented Would this be acceptable? Cheers Mark C As I wrote in http://jira.atlassian.com/browse/JRA-1397
 :
This solution with custom field is not good for us. Often, several persons can work on an issue. Not in the same time but because they do the same work. So if the issue is assigned to this group of persons. Each persons receive a mail and the first one who can work on it, assign the issue to herself. (See the comment of Tobias) Moreover, many projects involve several services. Then, when a user create an issue, he have to assign it to a service and not a person. This is the reason why we cannot assign automatically the issue to the project leader who can't see ALL the issue and reassign ALL of it !! Ann, unless I'm missing something, I don't see why you cannot achieve this using JIRA as it is. At our company (using 3.03 at the time) we had a pool of users who performed the same task, and any one of them could pick up the issue and assign to themselves. I created a dumy user called "techunassigned" with a name like 'Tech Pool' and an email like techunassigned@mycompany.com. I.T. set up this email as an alias which went to all members of the group, so for notifications, everyone in the group was notified when an issue was assigned to the pool. When a user assigned an issue to themselves from the pool, a notification would automatically be generated to the former assignee (the pool), so all would be informed. And all members of the pool had a portlet on their home page (dashboard) showing all issues assigned to the pool as well as to themselves. The browse project summary page also showed a good overview of issues because it showed how many open issues were assigned to the pool.
Yes, we do the same thing to replace the group assignation : we created generics users with generic email but the persons have to consult the mail. And they prefere to receive a mail in their own inbox and don't have to see each hour on JIRA if a new issue has come.
So I prefere using groups than generic users. With my setup, each user does receive an email in their own inbox, because the group e-mail has been set up by the I.T. folk to use that email alias and send emails to actual email addresses.
Indeed, I hadn't thought of this solution
Typo inssue = issue.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
New Feature
Resolved
Major
Assign an issue to a group
The problem with assigning issues to more tahn one person is that it is then impossibel to tell who is actually responsible for it. May I ask what is the motivation for assigning users to a group?
One possible solution is to create a 'group picker' custom field using JIRA's plugin sub-system which will allow to select a group the issue 'belongs' to. It will also be possible to find issues that have a certain group in this field and assign them to a particular person. For more information on creating new custom fields please see:
http://confluence.atlassian.com/display/JIRA/Customizing+Custom+Field+Types+Tutorial
Thanks,
Anton