# Time Tracking in Tickets **URL:** \ **Category:** Tickets & Conversations\ **Tags:** help-desk\ **Created:** [October 20, 2023, 2:53pm UTC](https://community.hubspot.com/t/time-tracking-in-tickets/92280 "2023-10-20T14:53:17Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![LNorman0](https://avatars.discourse-cdn.com/v4/letter/l/7bcc69/32.png) [@LNorman0](https://community.hubspot.com/u/LNorman0)\ **Post date:** [October 20, 2023, 2:53pm UTC](https://community.hubspot.com/t/time-tracking-in-tickets/92280/1 "2023-10-20T14:53:17Z")
We’ve been trying to use statuses as a means of tracking time spent on issues associated in tickets via ticket status. We’ve found the time on this to be extraordinarily wrong. Is there a better way to accomplish collecting data on how long my team is actively spending on each ticket (not just how long the ticket has existed)? ---
**Author:** ![DianaGomez](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/dianagomez/32/48035_2.png) [@DianaGomez](https://community.hubspot.com/u/DianaGomez)\ **Post date:** [October 20, 2023, 9:45pm UTC](https://community.hubspot.com/t/time-tracking-in-tickets/92280/2 "2023-10-20T21:45:04Z")
Hi @LNorman0, Thanks for reaching out to the Community! To calculate the time spent on a specific ticket status, you would need to create a custom property, as HubSpot does not have a built-in feature to track the exact time a ticket has stayed in each ticket stage. I have found some options that can help you. Please check them here. [Tickets - User time per ticket](https://community.hubspot.com/t5/Tickets-Conversations/Tickets-User-time-per-ticket/m-p/595941#M3232) - Solver @karstenkoehler [Create a custom report for (average) ticket time per ticket stage](https://community.hubspot.com/t5/Tickets-Conversations/Create-custom-report-for-average-ticket-time-per-ticket-stage/m-p/824069#M5382) - Solver @franksteiner79. Best regards, Diana ---
**Author:** ![mollmann](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/mollmann/32/38180_2.png) [@mollmann](https://community.hubspot.com/u/mollmann)\ **Post date:** [March 17, 2025, 2:24pm UTC](https://community.hubspot.com/t/time-tracking-in-tickets/92280/3 "2025-03-17T14:24:28Z")
Hi everybody, I wanted to share an update on additional functionality about ticket time in status reporting. Service Hub Professional and Enterprise customers will now have access to new data points about the time in ticket status. Each ticket will now have new properties that can be used in **report builders and segmentation** alike: - Date entered ticket status - Date exited ticket status - Latest time in ticket status (calculated using the two properties above) - Cumulative time in ticket status (for tickets that re-enter a ticket status multiple times) Users will also be able to access out-of-the-box reports with these new data points in the **[Help Desk Analyze Tab](https://app.hubspot.com/help-desk/l/analyze) as well as the [Service Hub Analytics Suite](https://app.hubspot.com/l/reports-list/templates/service/ticketTimeInPipeline?config=JTdCJTIyY3VzdG9taXplZCUyMiUzQWZhbHNlJTJDJTIycHJvY2Vzc29ycyUyMiUzQSU1QiU1RCUyQyUyMm1ldHJpY3MlMjIlM0ElNUIlN0IlMjJwcm9wZXJ0eSUyMiUzQSUyMnRpY2tldHN0YXR1cy4qX2R1cmF0aW9uJTIyJTJDJTIybWV0cmljVHlwZXMlMjIlM0ElNUIlMjJBVkclMjIlNUQlMkMlMjJwZXJjZW50aWxlcyUyMiUzQSU1QiU1RCU3RCU1RCUyQyUyMmRhdGFUeXBlJTIyJTNBJTIyVElDS0VUUyUyMiUyQyUyMmNvbXBhcmUlMjIlM0FudWxsJTJDJTIydW5pZmllZEV2ZW50JTIyJTNBbnVsbCUyQyUyMmV4dGVybmFsRGF0YVR5cGVTb3VyY2UlMjIlM0FudWxsJTJDJTIydW5pZmllZEV2ZW50VHlwZU5hbWUlMjIlM0FudWxsJTJDJTIyZGltZW5zaW9ucyUyMiUzQSU1QiUyMmh1YnNwb3Rfb3duZXJfaWQlMjIlNUQlMkMlMjJnZW5lcmF0ZWQlMjIlM0FmYWxzZSUyQyUyMmV2ZW50RnVubmVsJTIyJTNBbnVsbCUyQyUyMm9iamVjdFR5cGVJZCUyMiUzQW51bGwlMkMlMjJ0ZW1wbGF0ZSUyMiUzQW51bGwlMkMlMjJsaW1pdCUyMiUzQTE1JTJDJTIyZmlsdGVycyUyMiUzQSU3QiUyMmRhdGVSYW5nZSUyMiUzQSU3QiUyMnByb3BlcnR5JTIyJTNBJTIyY3JlYXRlZGF0ZSUyMiUyQyUyMnZhbHVlJTIyJTNBJTdCJTIycmFuZ2VUeXBlJTIyJTNBJTIyTEFTVF9NT05USCUyMiUyQyUyMnN0YXJ0RGF0ZSUyMiUzQW51bGwlMkMlMjJlbmREYXRlJTIyJTNBbnVsbCUyQyUyMnJvbGxpbmdEYXRlcyUyMiUzQW51bGwlMkMlMjJyb2xsaW5nRGF5cyUyMiUzQW51bGwlMkMlMjJkYXRlJTIyJTNBbnVsbCUyQyUyMmVudGlyZUN1cnJlbnRVbml0JTIyJTNBZmFsc2UlN0QlN0QlMkMlMjJvd25lcnMlMjIlM0ElNUIlNUQlMkMlMjJ0ZWFtcyUyMiUzQSU1QiU1RCUyQyUyMmN1c3RvbSUyMiUzQSU1QiU1RCU3RCUyQyUyMmZyZXF1ZW5jeSUyMiUzQSUyMkRBWSUyMiUyQyUyMmNvbmZpZ1R5cGUlMjIlM0ElMjJBR0dSRUdBVElPTiUyMiUyQyUyMnNvcnQlMjIlM0ElNUIlNUQlN0Q%3D&displayParams=JTdCJTIyc2FsZXNBbmFseXRpY3MlMjIlM0ElN0IlMjJzdWJBcHBLZXklMjIlM0ElMjJ0aWNrZXRUaW1lSW5QaXBlbGluZSUyMiU3RCUyQyUyMnNlcmllc09yZGVyJTIyJTNBJTdCJTIydHlwZSUyMiUzQSUyMnJhbmtlZCUyMiU3RCUyQyUyMnN0YWNrZWQlMjIlM0FmYWxzZSUyQyUyMmRhdGFDb2x1bW5zJTIyJTNBJTVCJTIyaHNfdGlja2V0X2lkJTIyJTJDJTIyaHVic3BvdF9vd25lcl9pZCUyMiUyQyUyMmNyZWF0ZWRhdGUlMjIlMkMlMjJoc190aWNrZXRfY2F0ZWdvcnklMjIlMkMlMjJoc19waXBlbGluZSUyMiU1RCUyQyUyMmFsbG93RHJpbGxkb3duJTIyJTNBdHJ1ZSUyQyUyMmNvbHVtbnMlMjIlM0ElN0IlN0QlN0Q%3D&chartType=BAR&editors=JTVCJTdCJTIydHlwZSUyMiUzQSUyMlFVSUNLX0ZJTFRFUiUyMiUyQyUyMm9wZXJhdG9yJTIyJTNBJTIySU4lMjIlMkMlMjJwcm9wZXJ0eSUyMiUzQSUyMmh1YnNwb3Rfb3duZXJfaWQlMjIlN0QlMkMlN0IlMjJ0eXBlJTIyJTNBJTIyUVVJQ0tfRklMVEVSJTIyJTJDJTIyb3BlcmF0b3IlMjIlM0ElMjJJTiUyMiUyQyUyMnByb3BlcnR5JTIyJTNBJTIyaHVic3BvdF90ZWFtX2lkJTIyJTdEJTJDJTdCJTIydHlwZSUyMiUzQSUyMlFVSUNLX0ZJTFRFUiUyMiUyQyUyMm9wZXJhdG9yJTIyJTNBJTIySU4lMjIlMkMlMjJwcm9wZXJ0eSUyMiUzQSUyMmhzX3BpcGVsaW5lJTIyJTdEJTJDJTdCJTIydHlwZSUyMiUzQSUyMlFVSUNLX0ZJTFRFUiUyMiUyQyUyMm9wZXJhdG9yJTIyJTNBJTIySU4lMjIlMkMlMjJwcm9wZXJ0eSUyMiUzQSUyMnNvdXJjZV90eXBlJTIyJTdEJTJDJTdCJTIydHlwZSUyMiUzQSUyMlFVSUNLX0ZJTFRFUiUyMiUyQyUyMm9wZXJhdG9yJTIyJTNBJTIySU4lMjIlMkMlMjJwcm9wZXJ0eSUyMiUzQSUyMmhzX3RpY2tldF9jYXRlZ29yeSUyMiU3RCUyQyU3QiUyMnR5cGUlMjIlM0ElMjJESU1FTlNJT04lMjIlMkMlMjJwcm9wZXJ0aWVzJTIyJTNBJTVCJTIyaHVic3BvdF9vd25lcl9pZCUyMiUyQyUyMmh1YnNwb3RfdGVhbV9pZCUyMiUyQyUyMmNyZWF0ZWRhdGUlMjIlMkMlMjJoc19hbGxfYWNjZXNzaWJsZV90ZWFtX2lkcyUyMiU1RCU3RCU1RA%3D%3D&dateRange=JTdCJTIycmFuZ2VUeXBlJTIyJTNBJTIyTEFTVF9NT05USCUyMiUyQyUyMnN0YXJ0RGF0ZSUyMiUzQW51bGwlMkMlMjJlbmREYXRlJTIyJTNBbnVsbCUyQyUyMnJvbGxpbmdEYXRlcyUyMiUzQW51bGwlMkMlMjJyb2xsaW5nRGF5cyUyMiUzQW51bGwlMkMlMjJkYXRlJTIyJTNBbnVsbCUyQyUyMmVudGlyZUN1cnJlbnRVbml0JTIyJTNBZmFsc2UlN0Q%3D&dimensions=hubspot_owner_id&metrics=JTVCJTdCJTIycHJvcGVydHklMjIlM0ElMjJ0aWNrZXRzdGF0dXMuKl9kdXJhdGlvbiUyMiUyQyUyMm1ldHJpY1R5cGVzJTIyJTNBJTVCJTIyQVZHJTIyJTVEJTJDJTIycGVyY2VudGlsZXMlMjIlM0ElNUIlNUQlN0QlNUQ%3D).** Let us know if you have any questions or feedback. ---
**Author:** ![zach\_threadint](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/zach_threadint/32/46318_2.png) [@zach\_threadint](https://community.hubspot.com/u/zach_threadint)\ **Post date:** [April 10, 2026, 3:43am UTC](https://community.hubspot.com/t/time-tracking-in-tickets/92280/4 "2026-04-10T03:43:22Z")
Hi @LNorman0 👋 In case this is still relevant to you (or anyone who stumbles across this post), you might find our app [**StopWatch**](https://ecosystem.hubspot.com/marketplace/listing/hubclock-by-thread-integrations-552213) helpful for these kinds of use cases. It includes **Start Timer** and **Stop Timer** custom workflow actions to help automate your HubSpot time-tracking use cases. The **Stop Timer** action has an optional input that allows you to **Exclude Out of Office Hours** , which allows for a bit more flexibility than HubSpot’s standard “Cumulative time In …” properties. I hope that proves helpful. Please let me know if you have any follow-up questions.