We don't want to change the way you work and require only two simple conditions that are essential to any workflow:

Tickets must be assigned to individuals
Tickets must transition from status to status

When timer starts?

In a simple scenario, timer starts when ticket moves to the active status like "In Progress" and ends when ticket is "Done". We don't exclude "To Do" statuses and use more conservative algorithms to capture time.

What if is there are many active tickets assigned to the same person?

This is where the magic happens. We would use user activity, like comments, ticket updates and other signals to determine where actual work happened. Having a ticket in active status doesn't guarantee that time will be captured. By design, Quantify prevents double counting, so there can't be more than defined hours per day captured.

What if a person has no tickets?

In a simple scenario, there will be zero hours captured. In case when a person is expected to always work on something and have a corresponding ticket, we recommend using Reminders feature to address such situation.

What about managers?

When turned on, Quantify can calculate management overhead per project or per team.

Personal settings

Each person can have different settings what also would define how time is captured. It can be more or less conservative and have an upper limit of hours.

What if a person is on vacation?

Public holidays are automatically excluded. Quantify integrates with some HR systems to match people and exclude the time off. Alternatively, you can import time off data from CSV file.
Was this article helpful?
Cancel
Thank you!