An unresolved-ticket count tells me how much is waiting. It does not tell me how much work arrived today, how much left the queue, or whether the backlog is moving in the right direction. That is the question behind my Freshservice Ticket Tracker.
The project began with manually recorded history and now includes a server-side API collector. The collector compares ticket states between pulls, recording changes such as new work, assignments, reopenings, completions, and reassignments. The dashboard brings that activity together with the unresolved balance.
One lesson is that a dashboard needs to explain its time window. At the start of a workday, today’s activity is naturally incomplete. Recent changes default the activity cards to the latest completed workday, which makes a quick morning glance more useful. Missing data also needs to stay distinguishable from a measured zero. No observation is not the same thing as no work.
The charts have evolved around readability. Unresolved tickets have their own vertical scale, while new and completed activity share another. Both scales remain visible when the plot scrolls on a phone. There is also a simpler dashboard for viewing the daily series without the rest of the detail.
Trend cards cover 7, 14, and 30 calendar days. They provide changes, coverage, and a fitted slope rather than turning two isolated numbers into a confident prediction. The estimate to reach zero is guarded and depends on the available history.
The tracker also records collector attempts, including failures. That matters because stale information can look convincing when it is presented neatly.
This is an aggregate view of progress, not a substitute for working the tickets themselves. My goal is to make the queue easier to understand—and eventually give that zero-ticket celebration something to do.