Reporting on % of tickets solved within a set period of time
답변함
2021년 12월 17일에 게시됨
I'm looking for help/a recipe for reporting on how many tickets (or the % of tickets) solved within 30 days and 60 days of being created. My organization has an expectation that 85% of tickets received will be solved within 30 days, and 98% will be solved within 60 days. I have looked into setting up SLAs to make this reporting possible but it doesn't seem to allow me to setup this specific SLA (i.e. ticket must be solved within 30 days of creation).
1
24
댓글 24개
Brandon Tidd
Hey 4550417520794
First, you'll need to create a standard calculated metric called “Timestamp day difference” with this formula:
Then here's the formula for the standard calculated attribute:
Hope this helps!
Brandon
0
Laurie Schafer
Hi,
I'm trying to do what Brandon Tidd suggested above (on February 20th) but I'm not sure how to do it. Can I have more descriptive instructions on this step?
I believe what needs to happen now is that you need to define [Time stamp hour difference] as a Metric in the dataset (opposed to an attribute). Then you would build the attribute using the custom metric.
Even better would be if I could get a formula for these exact brackets:
1 day
2 to 5 days
6 to 30 days
31 to 60 days
61 to 90 days
91 to 120 days
121 to 150 days
151 to 180 days
> 180 days
Thank you,
0
Brandon Tidd
Hey 1265341344269 -
No trouble at all! I believe what needs to happen now is that you need to define [Time stamp hour difference] as a Metric in the dataset (opposed to an attribute). Then you would build the attribute using the custom metric. Give that a go and let me know if that solves for this issue.
Cheers,
Brandon
0
Clarice Francis
Thank you for your help with this Brandon, and apologies for the back and forth. Unfortunately it did not recognise it, please see below
0
Brandon Tidd
Hey 1265341344269 -
Try wrapping VALUE() around your attributes
0
Clarice Francis
Hi Brandon,
Thank you for your help, unfortunately when I use the time stamp difference it gives me the error "formula_checker_invalid_addition_types" - please let me know if I am doing it wrong, I've pasted screen shots below too.
Thank you,
Clarice
0
Brandon Tidd
Hey there Clarice,
Ahh good call! In this case, I think you'd need to use the difference between the timestamps as your benchmark. This should produce a result in nb_of_hours. Let me know if that works for you!
Brandon
0
Clarice Francis
Hi Brandon, thank you not sure if I've done something wrong, but I get the error "formula_checker_invalid_addition_types"
In the original "DATE_DIFF([Ticket solved - Date],[Ticket created - Date],"nb_of_days")" I changed it to nb_of_hours but it shows 0, 24, 48, 72 etc. should I change [Ticket solved - Date]? Unfortunately, [Ticket solved - Hour] did not work
0
Brandon Tidd
Hey 1265341344269
Yes, this should be doable using a combination of the original code and the calculated metrics
Then use this to create your brackets of tickets in a another new custom attribute.
IF [Hours Between Created and Solved]<=4
THEN "4 Hours and Under"
ELIF [Hours Between Created and Solved]<=8
THEN "8 Days and Under"
ELSE "9 Days and Over"
ENDIF
Hope this helps!
Brandon
0
Clarice Francis
Hello
Is there a way to do this but measuring hours rather than days? For example
4 hours and under
8 hours and under
9 hours and over
Thank you
0
로그인하세요.