I think that you could achieve this in the following way:
- Create a new Boolean attribute on the group object called "No assignments".
- Add this to the Support Group window.
- Tick this box against any groups that you don't want assignments to go to.
- Modify the system filter that you have set on the Incident management - Assignment - Group attribute to also include the criteria: No Assignments Is Not Equal to (True).
So for my filter I have these criteria set:
Type is equal to (Support Group)
AND Users.User Is Equal To (User)
AND NoAssignments Is Not Equal To (True)
Seems to do the trick.
That worked fantastically!!
Thank you Karen!
I am un able to add any criteria to the assignment query. I also tried creating a filter that would not shoe those groups (the filter works) but when i apply that to the group object in the assigment window it does not work
Have you performed an iisreset on the server?
yeah ... I thought that was going to be the fix but did nothing. I find it strange that i can not add criteria to the assingment queries. I initialty tried to set this up in test enviroment and it would not let me edit the query as SA there. So i logged in as me on our production server just to see if i could add anything to the cretiria but that did not work either.
Try applying the filter on the Group Attribute in the Assignment object instead of the Assignment window.
There is already a default filter on that object ... that is the query that will not let me add any cretiria
Talked to support. They had the same issue in out of the box database. So i am recreating the query and see how that goes.
got it working. Thanks for the feedback. Originally i was looking at the wrong filter. then it was an boolean bahvior that we have seen before where the object does not wan to take the default value. Got all teh bugs worked out in my test enviroment so the production update should go allot smoother
Cool! Glad to hear you got it figured out.