Time to first response - changing status could also be a response

[Tobbe]

This is a really useful gadget for us to measure SLA but changing a new ticket to 'in progress' is also a response to the customer. Why does the gadget only consider a comment to be a response? is there a workaround?

[Tobbe · Accepted solution]

the workaround we found was to use the 'Average Time in Status' and then filter on issues in new state. this works fine for us since first response by our definition is when something is moved from new to in progress.

[Mark Kleinhaus]

Brilliant! Thanks.

[J]

I thought this was a bug until I found this thread - as it stands now the gadget should be called "Time to first comment" - the current name is misleading.

[J]

I thought this was a bug until finding this thread - as it stands today this feature should be called "time to first comment" since it doesn't actually show the time to first response (changing the status of a ticket from "submitted" to "in queue" in my case).

[J]

I thought this was a bug until I found this thread - as it stands now the gadget should be called "Time to first comment" - the current name is misleading.

[Jacob Maljaars]

I have exactly the same question.