SLA Business elapsed time Incorrect (changing p1 to p2 when incident state is OnHold)

Dileep Raju
Giga Guru

Steps to Raise a incident:
 Create Incident with p1 and state in progress.then put on hold awaiting caller. then, while on hold, change to p2.

result(issue):

the p1 and p2 SLAs appear to be working correcting in that the P1 was cancelled and the P2 added. However, when the P2 was added, it was added with the time from the beginning of the ticket, and does not take into account the time the ticket was on hold (p1 end time != p2 start time). The P4 SLA should start with the same business elapsed time as the P1.

expected:
p1 and p2 elasped business time should be same(p1 end time = p2 start time)

5 REPLIES 5

Hi @Mohan Mallapu 
It is not working as expected.

Now p2 elasped business time = 0
It is not addined p1 OnHold time.
p1 = 1min
p2 = 0 min
We required P2 also 1min