You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I wanted to provide a quick overview of how the logic behind how time tracking works when using different date ranges in a report. This seems to be a somewhat common request, to understand why the period selected is days but the summary metric shows in hours (for example).
Firstly, from a code perspective, the report summary section metrics (months/days/hours/minutes) is quite implicit, internal and dynamic. It doesn’t use the select period and it’s not designed to use the time period selected either. The time period is only for splitting reporting data into buckets. In my test case (screenshot below) the bucket is one day:
The metric is determined in the report frontend by comparing the max Y axis value in the report data with 3 thresholds, 6 months, 30 days and 2 hours. In my case, the max Y axis is the max Time to resolution time among all the one-day buckets.
If max Y > 6 months, we use months,
If max Y > 30 days, we use days,
If max Y > 2 hours, we use hours,
Otherwise we use minutes.
In conclusion, this logic is not impacted by how long the date range you choose is and which Period you choose in the UI. This was also how it was designed and implemented by our development team.
Thanks for reading!