I would like to handle incident by Assignment group. Currently my team is handling tickets by assgnee and I would like to use both cases like
- Assignment group then
- Assigned to or (assignee)
I want to manage the tickets in a better way
JIRA doesn't allow assigning to groups. The closest workaround is to create a dummy ID that can't logon and use a distribution list for the email. HOWEVER, the 'assigned to me' filter won't work and from my and others experience issues that aren't assigned to a real person don't get worked. A better option, I believe, is to have a select list with functional groups you can assign for searches and leave the assignee to the group lead.
I only have experience with Outlook. You need to request from the outlook administrator group a distribution list be created and someone be made the owner and administrator of the list. when it is created you can add/delete people from the list. The list will usually have a logical name like email@example.com Then you create a user in JIRA with the list email. Remove the user from the logon list so it doesn't count against licenses. Add the user to the needed roles in the project. When the user gets notifications the distribution list will in turn email every member of the list.
I think the responses here are correct; there is no easy way to do this. I will offer another possible alternative. You may be able to create a custom automation rule, add a new group, and assign that group upon issue creation.
Step 1: Go to the left navigation panel within the project, look for “Automation”. Then click on “Add rule”, choose “Custom rule” at the top. Click “Continue.”
Step 2: Under “When this happens…” choose “Issue Created.” click Add.
Step 3: Under “Then do this…” choose “Edit Issue” Field “Assignee Group”
However, for this to work you will first need to create the group under “User Management.” To do this you can type “gg” within your project and you will see the option for “User Management”. Click on “Groups” create the group you want to make for the issue assignees. Add the users you wish to include to that new group. This new group should now be an option under step 3 above. Note, the field “Assignee Group” will also need to be on the request type form and the resulting issue.
Between Steps 2 and 3 above you can add a condition. This is an option as you build the custom rule. See the button “Add condition”. This allows you to narrow down which issues will be affected by this new automation rule. (You may have to create new issue types, etc. there is no easy way to fulfill your request as mentioned by the others who have responded to your post.)
I have not tested this so you may have to play with it for a while to make it work (or it may not work at all) The other option is to try a post function on the “Create” transition and try the same method. Create a group, add users, etc. I would probably use the “Set field value” post function and try your best to tell the post function to do what you want. Select “Issue Fields” under Value. Select “assignee group”. But again, this too is a precarious work-around.
I hope this helps.
@White Software - I have installed the plugin but i don't see any way to configure with workflow. I've gone through the doc: https://whitesoftware.atlassian.net/wiki/spaces/GGA/overview .
Let's say, i want to assign the ticket to group of people once approved by manager. How do I configure with workflow?
Hello @Selva G,
This looks like a very good use case but it's a not thought by us previously. In this case, we'll add such an update on transition functionality to Groupee.
Even though, I can suggest a way for now. If you set the value of Groupee custom field to related group on a transition it will assign the issue to someone from that group. To do that you may use one of these plugins,
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events