Time tracking

Time belongs to the work it explains.

Log time on the issue it was spent on, by date or across a date range. The issue, its parent, the timesheet and the time report all add up the same entries, so every total leads back to an issue.

Join the beta Read the time tracking manual

See the time workflow

ACME/ACME-12/Add spent time

DateDate range

Date: 8 Oct 2026
Time spent: 1h 25m
Type: Development
Note: Expired links land on an explanation with a Request a new link button.

+ Add another recordAdd spent time

1Logged on the issue it explains

ACME/ACME-12/Spent time

Invite link blank after it expires

Type: BBug
Assignee: ALAlex Lee
Estimation: 2h
Spent time: 1h 45m of 2h

2 records1h 45m

ACME-128 Oct 2026 · Alex Lee · Development1h 25m
ACME-126 Oct 2026 · Alex Lee · Development20m

2Added to the issue’s spent time

Reports/TimesheetThis week

ALAlex LeeMon 51h 30mTue 61h 50mWed 745mThu 81h 25mFri 91h

Alex Lee · Thu 8 Oct 20261h 25m

ACME-12Invite link blank after it expiresDevelopment1h 25m

3Behind the timesheet cell for that day

One entry, three places: Alex logs 1h 25m of Development on ACME-12 for 8 Oct 2026. Hand-drawn product views with fictional data.

From a logged hour to the time report.

One set of entries, read five ways. Pick a step to see what the person at that point sees.

ACME/ACME-10/Add spent time

DateDate range

From: 5 Oct 2026
To: 6 Oct 2026
Time spent: 1h 30m
Type: Development

Writes 2 records of 1h 30m, one per working day. Weekends are skipped, and each record can be changed or deleted on its own.

+ Add another recordAdd spent time

Written as you would say it

2h, 1h 30m, 1d. A day and a week follow the organisation’s working calendar. The type starts at the project’s default, and the note is markdown.

Three ways in

Below the comment box, the + beside Spent time in the sidebar, or the issue’s Spent time tab.

ACME/Issues/ACME-3

EEpic

Make invitations clearer

Estimation: 2d
Spent time: 1d 3h 45m of 2d

SubtasksSpent time

ACME-10Invite landing shows the inviter4h 15m
ACME-15Resend invite from the members list4h 15m
ACME-12Invite link blank after it expires1h 45m
ACME-14Invite email subject names the org1h 30m
ACME-3Make invitations clearer1d 3h 45m

Acme’s working day is 8h, so 1d 3h 45m is 11h 45m. Delete a subtask and its time comes off the epic; restore it and the time comes back.

ACME/Settings/Time tracking

Time tracking: On for this project
Estimation field: Estimation built in
Spent time field: Spent time built in

Work item attributes

Work typeBuilt in, cannot be removed
+ Add attributeBillable with Yes and No, say. Picked beside Type when logging.

Work types

Development default
Documentation
Implementation
Investigation
Maintenance
Observation
Testing

Choose a duration field of your own as the Estimation and the sidebar, the sprint’s remaining work and the time report read it instead.

Reports/TimesheetOpened by Casey Kim

SOSam OrtizMon 545mTue 6Wed 72hThu 81h 15mFri 930m

Sam Ortiz · Wed 7 Oct 20262h

ACME-15Resend invite from the members listDevelopment · logged by Casey Kim2h

Casey logged this on Sam’s behalf as a Project Admin. It still belongs to Sam, who can edit or delete it.

Reports/TimeExport CSV

project: ACMEBy issueThis week

Issue	Spent	Estimate	Difference
ACME-10Invite landing shows the inviter	4h 15m	5h	45m
ACME-15Resend invite from the members list	4h 15m	6h	1h 45m
ACME-12Invite link blank after it expires	1h 45m	2h	15m
ACME-14Invite email subject names the org	1h 30m	1h	−30m
ACME-11Swimlane header overlaps count	1h 30m	2h	30m
ACME-8Saved view count is stale	45m	1h	15m
Total	1d 6h	2d 1h	3h

ACME-3 has no row of its own: the report adds up entries by the issue they were logged on, so a subtask’s time is counted once. A negative difference is time over the estimate.

See where the week went, down to the issue.

People as rows, days as columns, totals both ways, non-working days marked. Open a cell, or a person’s total, to see the entries behind it. Each one names the issue it was logged on.

Reports/Timesheet5–11 Oct 2026 · Everyone

Person	Mon 5	Tue 6	Wed 7	Thu 8	Fri 9	Total
ALAlex Lee
CKCasey Kim
SOSam Ortiz
Total	3h 15m	2h 20m	3h 45m	3h 10m	1h 30m	1d 6h

Alex Lee · Tue 6 Oct 20261h 50m

ACME-10Invite landing shows the inviterDevelopment1h 30m
ACME-12Invite link blank after it expiresDevelopment20m

Fictional data. You see time logged on any issue you can open, whoever logged it. How timesheets work

Where the totals meet.

Every figure on this page is a sum of the same 14 entries. Here is the arithmetic.

ACME-12

20m + 1h 25m = 1h 45m

Its two entries sit in Alex’s cells for 6 and 8 Oct. The same total shows in the issue’s sidebar, the epic’s subtask list and the time report’s row.

ACME-3

4h 15m + 4h 15m + 1h 45m + 1h 30m = 1d 3h 45m

The epic’s spent time is its subtasks’ entries. The time report gives it no row, so nothing counts twice.

The week

6h 30m + 3h + 4h 30m = 1d 6h

The timesheet’s corner and the time report’s total. Acme’s working day is 8h, so 1d 6h is 14h.

On where it helps, off where it does not.

Time tracking is a setting on each project, on for a new one. A Project Admin can switch it off: Estimation and Spent time leave that project’s issues and nobody can log time there. Nothing is deleted, so switching it back on brings every record back.

The time report, timesheets and the other reports Custom fields as your Estimation or Spent time

For learning.

Put an estimate on the issue and the sidebar shows what has been logged against it, turning red once it goes over. The time report puts estimate, spent and the difference side by side for every issue in scope.

For accountability.

Every addition, change and removal of a record is kept in the issue’s history. You edit or delete your own records; Project Admins can edit or delete anyone’s, and deleting asks first.

For client work.

Add a work item attribute such as Billable, group the time report by it, and export the same numbers to CSV. Each row still traces back to the issue the time was logged on.

Who logs for whom.

Contributors and above log their own time; Observers read it. Project Admins and organisation admins can log for any member who could log their own. The record shows who logged it and stays the author’s to edit.

Sam Ortiz · 7 Oct 2026 · 2h Development · logged by Casey Kim

Questions about logged time.

Timers, totals, permissions and the working calendar. Short answers here, the rules in the manual.

Is there a running timer?

No. You enter the time you spent, on one date or across a date range, written the way you would say it: 2h, 1h 30m, 1d. A range writes one record per working day, and each record can be changed or deleted on its own. Time tracking in the manual

Can someone log time for a colleague?

Project Admins and organisation admins can, by choosing the colleague as the author. Anyone who could log their own time in the project can be chosen, never an Observer. The record shows who logged it, and it belongs to its author, who can edit or delete it like their own. Permissions

Does a parent issue count its subtasks’ time twice?

No. A parent’s spent time includes everything logged on its subtasks, so an epic shows the whole effort beneath it. The time report adds up the entries themselves, so a subtask’s time is never counted again through its parent. Deleting a subtask takes its time off the parent, and restoring it brings the time back.

Can we turn time tracking off for one project?

Yes. It is a setting on each project, and a Project Admin can switch it off. Estimation and Spent time then disappear from that project’s issues and nobody can log time there. Nothing is deleted: turn it back on and every record is where it was.

What does 1d mean in a total?

A day and a week follow your organisation’s working calendar. With an 8-hour working day, 1d 3h 45m is 11h 45m. The time report and its CSV export use the same units, and totals close the file. Reports

Can an AI agent log or read time?

Yes, through the MCP server. An agent logs time on an issue key with a duration, a date or range, a work type and a note, and its token needs the time:write scope. It reads timesheets and the time report as the same table the chart is drawn from. MCP and AI agents

Ask something else

Log the first hour against a real issue.

Join the beta, open a project and add spent time from any issue. The timesheet and the time report fill in from there.