We appreciate you taking the time to vote and add your suggestions to make our products awesome! Your request will be submitted to the community for review and inclusion into the backlog.
We recommend reviewing what is submitted before posting, in case your idea has already been submitted by another community member. If it has been submitted, vote for that existing feature request (by clicking the up arrow) to increase its opportunity of being added to Cireson solutions.
For more information around feature requests in the Cireson Community click here.
We recommend reviewing what is submitted before posting, in case your idea has already been submitted by another community member. If it has been submitted, vote for that existing feature request (by clicking the up arrow) to increase its opportunity of being added to Cireson solutions.
For more information around feature requests in the Cireson Community click here.
Outlook Console, template selection based on support group
Adam_Dzyacky
Product Owner Contributor Monkey ✭✭✭✭✭
As an SCSM admin, you have to default the Outlook console's Work Item creation to a single template - it would be awesome if multiple templates could be defined so that based on the user initiating the Outlook task it picked up their Support Group and then used that to drive what template was actually picked.
I suggest this as users new to SCSM (or those even intimately familiar) leverage the Outlook console to get items into SCSM faster and more consistently. But as SCSM becomes deployed to more departments within an org the possibility of the person kicking the task off and forgetting to change this value to something (that would be in their queue scope) increases dramatically. What's more, the idea of queues/permissions is something more casual user's of SCSM have no concept of and thus create Work Items that either are accidently created in someone else's queue OR worse go completely unnoticed.
I suggest this as users new to SCSM (or those even intimately familiar) leverage the Outlook console to get items into SCSM faster and more consistently. But as SCSM becomes deployed to more departments within an org the possibility of the person kicking the task off and forgetting to change this value to something (that would be in their queue scope) increases dramatically. What's more, the idea of queues/permissions is something more casual user's of SCSM have no concept of and thus create Work Items that either are accidently created in someone else's queue OR worse go completely unnoticed.
3