/build/static/layout/Breadcrumb_cap_w.png

Ticket Assignements

I'm trying to figure out if in a ticket rule to referr to the account that is logged into KACE.

The idea is that if a support person is logged in and assigns a ticket to themselves, upon save it react to whatever the rule is set to do. Like upon save change status from "new" to "work in progress."

0 Comments   [ + ] Show comments

Answers (3)

Posted by: GillySpy 14 years ago
7th Degree Black Belt
0
That sounds like a wizard rule:

step 1:
owner contains _
and status = new


step2:
status = work in progress
Posted by: londeaux 14 years ago
Second Degree Green Belt
0
Yeah figured that part that out, but we want the owner of ticket and the person who's logged into KACE to be the same. Otherwise, if the ticket is assigned to someone else it becomes "work in progress" and the owner may not know they have a new ticket assigned to them.

We're just trying to automate as many steps as possible.

Our owners are already complaining about the escalation emails.
Posted by: GillySpy 14 years ago
7th Degree Black Belt
0
Oh i see, currently there is no way for a rule to determine who is logged into the kbox. However, there is a way for a ticket rule to determine who made the change.


Whatever rule you get out of the above you could modify it to join in HD_TICKET_CHANGE table.

JOIN HD_TICKET_CHANGE ON HD_TICKET.ID=HD_TICKET_ID and HD_TICKET_CHANGE.ID=<CHANGE_ID> and OWNER_ID=HD_TICKET_CHANGE.USER_ID

That would mean we know the change in hand was made by the owner.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

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