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?
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.