Measure time based on ticket status. | Community
Skip to main content

Measure time based on ticket status.

  • October 31, 2019
  • 5 replies
  • 0 views

Halo everyone.

i have the difficulties to measure time handling based on ticket status. 

 

the instance case: there is new ticket then taken by the agent, that ticket is changed by the agent become open then escalating to partner as on hold and in the end is solved.

would anyone help me to calculate handling time:

1. new - to open
2. open - to on hold
3. on hold - to on hold (conditional case)
3. on hold - to solved.

i have tried using metric new, open, and on hold status time but i am doubt becuase that metric only measure 1 reply per 1 diffrenent status.

thanks before


 

5 replies

ZZ55
  • October 31, 2019

Agus

If you use the Support Tickets [default] dataset, you can find the total time a ticket has spent in each status. However, the metric names are a little different.

Here is an extract explaining the metric names:

And the full reference is here.


  • Author
  • November 4, 2019

Hi Graeme.

 

Thank you so much for the answear. would you mind to help me one more regarding of how to measure the time handling by updated and public comment?


Many Thanks,


ZZ55
  • November 4, 2019

Agus

It sounds like you are after the first public reply time?


  • Author
  • November 4, 2019

Hi Graeme,

 

Thanks for the answear. But not only the first public reply but also until that ticket is solved. 

for instance, i would like to calculate:

1. from that ticket new and change to on hold or solved
2. or that ticket from on hold status and than escalated again  in the on hold status as well

3. or from on hold to solved. 

 

Thank you before

 


ZZ55
  • November 4, 2019

Agus

To do the query, you nee to use the Ticket Updates Dataset. You can see an example the duration of fields here.

Here is an example of the metric from status hold to status solved:

 

However, I would not recommend this approach as there is no guarantee that the status will follow the pattern that you expect and the total duration of all your metrics may be greater than the life of the ticket.