Global Operators Group
Best Answer
-
Joe_Burrows Cireson Devops Super IT Monkey ✭✭✭✭✭Hi Margarete
Thanks for the additional information , the Cireson Portal behaves a little differently in this scenario compared to SCSM as you have already noticed.Do you know why it is working within scsm but not within the cireson Portal.We want to avoid that tickets are assigned to endusers. As far as I know it is not possible to nest the assign groups in the AD analyst Group because they are mailing lists.
By design the Cireson portal is to show all members of the analyst AD group (including groups if they have been nested), which is a different behavior to the SCSM console.
Id recommend raising a feature request if you wanted to see if we can change this to parity the SCSM consoles behavior of scoping via global operator group.
Hope that helps
Regards
Joe5
Answers
By default the "Assigned to" Field is filted by Analysts, so users from your analysts AD group should appear in the picker.
Is this not happening?
Regards
Joe
Hello Joe,
the users appear but not the groups.
Regards
Margret
As the picker is scoped by analysts it will only show members of your AD analysts group, you would need to nest the group objects in your AD Analyst groups to have them appear as an option on the picker.
OR
You could create a custom form and set the filterbyanalyst to false so all objects appear:
See example here for how to create custom forms.
Hope that helps
Regards
Joe
Hello Joe,
thank you very much for your answer. I think I have to give some more Information. In the scsm console I get alle users and groups who are in my scsm group GLOBAL OPERATORS GROUP. That is what I want for the portal. Do you know why it is working within scsm but not within the cireson Portal.We want to avoid that tickets are assigned to endusers. As far as I know it is not possible to nest the assign groups in the AD analyst Group because they are mailing lists.
If we set filterbyanalyst to false we get too much users appearing in the picker.
Best Regards
Margret
Thanks for the additional information , the Cireson Portal behaves a little differently in this scenario compared to SCSM as you have already noticed.
By design the Cireson portal is to show all members of the analyst AD group (including groups if they have been nested), which is a different behavior to the SCSM console.
Id recommend raising a feature request if you wanted to see if we can change this to parity the SCSM consoles behavior of scoping via global operator group.
Hope that helps
Regards
Joe
We nested the affected groups to the analyst AD group. The groups must be global otherwise you are not able to nest them. Everything works fine now. There is no need to change this behaviour.
Thank your very much