# Time tracking in Todomator: timers, manual entries and the minimum log time

> How Todomator records the time spent on a ticket: a start/stop timer, manual entries, the minimum and maximum minutes, and how the total of a ticket is kept.

Framework: todomator
Product: Todomator (todomator@1.7)
Language: en
Content-SHA256: 846740c7eea059a9159b38ff4b39d454fe32cbf6fbcc52d53c7ed2950844d9e5
Snapshot: c0700e321579725c5cf4f5ace1ad7d2866d1b4f93c24a63c0b41b6b7998e976c
Sources: 
Review: not-recorded

Todomator records working time in the table `tbl_ticket_time` and keeps the sum in the field `worked` (minutes) of the ticket. The actions are in `schemas/tickets.js`.

## The timer

- **Start** (`logwork_start`): opens a timer on a ticket for the current user. If the ticket was `pending`, its status changes to `open` automatically.
- **Stop** (`logwork_stop`): closes the timer and adds the elapsed minutes (rounded up) to the ticket. A single timer counts at most **8 hours**, and never less than the setting `minlogtime`.
- **Open timers** (`logwork_open`): lists the timers that the user has running.

## Manual entries

`logwork_create` adds an entry with the ticket, the minutes, a date and an optional note; `logwork_update` and `logwork_remove` change or delete it, and after an update the total of the ticket is recalculated from all its entries. Entries are never smaller than `minlogtime`. You can also pass `worked` when you create a ticket (also through the [API](/en/todomator/create-tickets-with-the-api/)): Todomator then records an entry of that many minutes.

## The setting

`minlogtime` (minutes, 1 by default) is in the [settings](/en/todomator/settings-and-database/). It is the shortest entry that Todomator records, which avoids rows of zero minutes.

## Notifications and billing

Every logged time notifies the other people of the ticket and refreshes it live for those who can see it. The flag `isbillable` of the ticket (inherited from the folder) marks the time that you bill, and the premium plugins of reports and user workload build on these records.