/build/static/layout/Breadcrumb_cap_w.png

Suggestions on how to handle an end user task

I have a need to ask employees to complete a task.  I have a queue Ive created for the tasks and a rule which is setup to submit a ticket to that queue with instructions which will of course appear in the summary.

Since the email is coming from the SMA I need to either set the submitter or the owner of the ticket.

I dont like the idea of allowing all users as owners for the queue.  Seems to me it grants too much access.  But still not sure what the best path is.  

If I make the  submitter the name of the individual, ($ticket_submitter_name)  can the submitter close the ticket when it is done?  


Any thoughts on how to handle this please?





0 Comments   [ + ] Show comments

Answers (1)

Posted by: Hobbsy 2 weeks ago
Red Belt
0

Great point, when trying to get any employee to engage on a ticket they need to be the submitter or the ticket owner and none of us want everybody to be ticket owners. The easiest way to do this is just to switch in the user as the submitter, you can do that by simply adding their ID into the HD_TICKET.SUBMITTER_ID field.

Another way we are playing around with is making the ticket owner label dynamic, in other words when you need the user to edit the ticket ad their ID to a label used as ticket owners and once their task is done remove them from the group, you should be able to do this using a ticket rule or two.


Comments:
  • Thanks Hobbsy. We always have to think outside the box when it comes to Kace because very little is in the box. - barchetta 2 weeks ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ