There are two built-in metrics you can use in Analytics that sound almost the same, but when applied give different results:
Resolution time in calendar hours
Resolved tickets lifetime in Calendar hours
What exactly is the difference?

There are two built-in metrics you can use in Analytics that sound almost the same, but when applied give different results:
Resolution time in calendar hours
Resolved tickets lifetime in Calendar hours
What exactly is the difference?
I think I figured this out…
Resolved tickets lifetime in calendar hrs = time from created to Closed status
Resolution time in calendar hours = ttime from created to Resolved status which is 0 if the ticket is not resolved before it is closed!
Resolution time refers to the amount of time it takes to resolve an issue, from the moment it's identified to when it's fully addressed or closed. It's crucial for tracking performance and ensuring customer satisfaction.
but testing seems to confirm my statement otherwise.
I was by the way wrong in stating “which is 0 if the ticket is not resolved before it is closed!”, I had a report filter on unawares, the correct seems to be ‘which is the same as the above, if the ticket is not resolved before it is closed’.
Solution:
The difference lies in scope:
Use Resolution time for tracking efficiency and Resolved tickets lifetime for a full view of ticket handling history.
Hi
Thank you for bringing this up.
The difference between the two metrics lies in their scope of measurement:
Resolution Time in Calendar Hours:
Resolved Tickets Lifetime in Calendar Hours:
In summary:
Thank you
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.