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

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?

5 answers

1 accepted

3 votes
Accepted answer

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.

Brilliant! Thanks.

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.

I have exactly the same question.

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.

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).

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Oct 31, 2018 in Marketplace Apps

Marketplace Spotlight: Zephyr

Hello Atlassian Community! Each month, we run a series of Spotlights to highlight Marketplace vendors and apps that our team thinks this Community would find valuable. In last month's Spotlig...

348 views 0 1
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you