Restrict Notifications/Emails for Assignment Group All Enabled Users

[JamesNowe]

Hello,

We've had a few instances where a user was trying to assign a ticket to another user. They didn't know what group they belonged to, so they set the Assignment Group to All Enabled Users which is fine. However, they didn't choose the user under Assigned to and assigned the ticket, assigning the ticket to the All Enabled Users Group. All of our Enabled Users received notifications regarding the ticket.  We want to restrict users from being able to do this. 

Anyone have an idea what would be the best way to handle this?

James

[JenniferRah]

I assume this is a group that is specific to your environment. The easiest way to prevent this from happening is to remove the "itil" type from that group. Then the group would not be allowed to be assigned to things like Incidents. 

[JamesNowe]

Thanks for the reply Jennifer. The group contains all of our users\members. It contains the sn_ind_rmt_help.requester role only, which contains all of the groups our members belong too. All of our groups contain the itil role. For the All Enabled Users group would it work if I set Inherits to False?

[JenniferRah · Accepted solution]

By default, the Assignment Group is restricted to groups with the Type of "itil" or with no Type. It looks like your group has no Type. We created a custom type called "No Assignment" and added that type to groups that don't need to be able to be assigned to tasks. That sounds like an easy fix for you if you haven't customized that criteria.

[JamesNowe]

Thanks Jennifer. The fix you suggested was easy to implement and works great.