Forum Discussion
Reaction-/Resolution time calculations (with a twist)
1: Yes I'm creating measure. Actually also tested as calculated column which will result in circular dependencies error.
2: Columns are set as date/time in source.
3: Also using actual names for sure as otherwise function would return an error which it doesn't now
I tested further and if I create a table in my report with ID and these measures as a value Im getting following data:
ID - Reaction Time - Resolution Time
38 - 30.12.1899 0:00:00 - 14.1.1900 15:26:21
39 - 30.12.1899 0:00:00 - 14.1.1900 14:46:49
.
.
So it is calculating something but gives weird results.
Any ideas?
Figured out something!
The first modified timestamp is always the same as ticket creation date. So the function always give 0 seconds for reaction time. The timestamp which is the same as "ticket created" timestamp needs to be ignored in function.
- Anonymous9 years agoNot applicable
Would datediff work in this scenario? I have used it before but that modified timestamp and distincting ticket ID:s gives me headache.
- Vvelarde9 years ago
Community Champion
Anonymous
Hi, try with these measures.
ReactionTime = DATEDIFF ( MIN ( Table1[Ticket created] ), CALCULATE ( MIN ( Table1[Ticket modified] ), FILTER ( Table1, Table1[Ticket modified] <> MIN ( Table1[Ticket created] ) ) ), HOUR )ResolutionTime = DATEDIFF ( MIN ( Table1[Ticket created] ), CALCULATE ( MAX ( Table1[Ticket modified] ), FILTER ( Table1, Table1[Ticket modified] <> MIN ( Table1[Ticket created] ) ) ), HOUR )- Anonymous9 years agoNot applicable
This works! Any hints on how I can get output in Days and hours instead of full hours?
Thank you very much both for contributing!