Resolution time

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.

​@xivlauncher, I am not sure that really clarifies the distinction between the two metrics though…

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:

• Resolution time in calendar hours measures the time taken to resolve a ticket from the moment it was created.
• Resolved tickets lifetime in calendar hours includes the entire lifecycle of the ticket, even if it was reopened before final resolution.

Use Resolution time for tracking efficiency and Resolved tickets lifetime for a full view of ticket handling history.

​@zafarkhan987, thank you for your input, you make good sense and I will investigate further how intermediate resolutions and reopenings affect these times to make sure. Did you find this information in a Freshdesk help file or similar? Or what is your source for stating what you do?