Time Tracking
Time tracking captures minutes spent on a specific ticket or sub-task. It's used by Consulting projects to record effort and support billing. (For a free-form daily summary that isn't tied to one ticket, use the Work Log instead.)
Logging time
On a ticket or sub-task in a Consulting project, add a time entry with:
| Field | Notes |
|---|---|
| Minutes | Amount of time spent |
| Spent on | The date the time applies to (defaults to today) |
| Note | Optional description of the work |
Each entry is attributed to you. Time can be logged against either the ticket or one of its sub-tasks.
Who can log time
Logging time requires the workspace:time:log permission. By default both the Lead and Member roles in a Consulting project have it; Viewers do not. Admins can adjust this in the Roles module.
The four hour fields
Separately from logged time entries, a Consulting or Dev ticket carries four hour figures, each captured at a different point in its life. Support tickets use none of them — they run on a due date — and neither do Epics.
| Captured when | Field | Meaning | Entered by |
|---|---|---|---|
| The ticket is created | Pre-approval hours | The effort budget agreed with the client up front — the ceiling the work is expected to stay inside | Whoever creates or edits the ticket |
| Work moves to In Progress | Estimate hours | The assignee's own estimate of the effort required, given before starting | The assignee |
| The ticket is marked Fixed | Actual hours | The real time it took | The assignee |
| The ticket is Closed | Billable hours | The number that goes on the invoice — may differ from actual hours by agreement | A Lead |
:::warning Going over the pre-approval needs a Lead If estimate hours exceeds pre-approval hours, the ticket is flagged and cannot be marked Fixed until a Lead approves the overage. Look for Ask for approve estimate on the ticket; a Lead can approve or revoke that approval at any time. :::
:::note Nothing here is calculated Every one of these four is typed in by a person at that step. None is summed automatically from time entries or anything else. If a number looks wrong, it was entered wrong — there's no hidden calculation to untangle. :::
All four stay editable afterwards for anyone with permission to manage the ticket, in case a figure was entered incorrectly.
Reporting
Logged time rolls up into Analytics — the Worklog table summarizes time by person and project over a date range, and the Monthly Timesheet export lays it out as a daily grid.
Why the timesheet's two hour columns differ
| Column | Comes from |
|---|---|
| Working / hours worked | Time entries logged against that day |
| Actual hours | Each ticket's own actual hours field |
These are recorded independently, so they will not always match. A gap between them is expected, not an error.
Work Log is not an hours feature
The name invites confusion, so plainly: the Work Log is a daily diary — a date, a written summary, the tickets it relates to, and who you're sharing it with. It has no hours field at all and is not tied to billing. To record effort, use the fields above or a time entry.