Hi Susan,
Thanks! Now to figure out why the 'Response Time' field is on our development configuration but not our production one..hmm
Response Time is just a name of a SLA. IT's one of the out of the box ones, but you can certainly remove, rename, customize....
So maybe the development one was removed, renamed...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kevin,
Did you try using the Automation - Send Email for that scenario?
Susan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Susan,
I looked in Automation for that and I'm sure that would work but how would I be able to have it look at the Calendar?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kevin,
So Trigger would be issue created. You would need to have a response SLA that starts running when the issue is created that is tied to your desk hours.
This filter:
"Response Time" != withinCalendarHours()
Will find any requests raised outside of the regular hours.
Hope that helps...Susan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I use the "Standard Support 8-5 Calendar"
It is Monday to Friday 8:00 - 17:00
I know my SLA works
However, when I create a nw ticket at 19:00 I get
Status is "NOT EXECUTED"
Issue matches:
"Time to first response" != withinCalendarHours() is failing
I include Screenshots:
Can you please help my figure out what I'm doing wrong?
Thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.