Jump to content

SLA - Timers Not applying to some tickets ?


Recommended Posts

This is a bit of a mystery.

Some tickets going through the system are not picking up Request Resolved time, this is only happening with one SLA level which is LOW, but then again not all the time.

So date logged, resolved and closed are all populated, but only a few tickets set to LOW are reporting a value for Within Resolve Time.

As you can see some Email tickets work, some do not, same goes for Analyst tickets.  All Self Service do not work. 

Any pointers ?  Where should I be looking ?

image.thumb.png.257ea1a872eb6aeb6a6da427a71ae9e4.png

 

Link to comment
Share on other sites

@Victor  Interesting, made some changes, all is working, except for tickets coming in via the Portal :(

Tested Analyst and Email, both worked fine.  Tested with Portal, and as you can see from below, nothing applied.

Any pointers always received gratefully.

image.thumb.png.f5b5bd8b5e5f021321fb4f65305eb388.png

Above graphic only has my name listed, so no data issues :)

Link to comment
Share on other sites

@Victor It is working, down to the location of the Start Timer in the BPM process.

Thanks for helping.

The node was too early in the process and so when the progressive capture came into play, it did not take effect.

image.thumb.png.0265ae361588b39c12d1de9f089262b8.png

:)

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...