Worklogs & time

Estimates

The Time tracking block in an issue’s details panel shows three numbers and a bar:

• Original estimate — how long you expected the work to take. Click it (Edit original estimate) to set or change it.
• Time spent — the total of all worklogs.
• Remaining — what is left of the estimate.

Durations are written in weeks, days, hours and minutes: 3w, 1d, 2h 30m, 4d 2h. Anything else is rejected with a message that shows valid examples.

Logging work

1. Open the issue and press Log work in the time-tracking block or the Work log tab.
2. Enter Time spent (for example 2h 30m), the date and time the work happened if it was not just now, and optionally a description (“What did you work on?”).
3. Press Log Work.

The Work log tab lists every entry with the author, date and comment, plus Total time spent. To correct an entry press Edit Worklog and save with Update; to remove one choose delete and confirm. Everyone may edit their own worklogs; changing someone else’s needs the Edit all worklogs or Delete all worklogs permission, which administrators typically give to team leads.

Seeing time across issues

• The epic report can total in hours instead of issues or story points.
• Dashboards have gadgets for time and resolution (Resolution time, Average age).
• The REST API returns worklogs per issue and across a date range (API).

The Time in status view under the issue’s Transitions tab shows how long work sat in each status. That is calendar time, not logged work — see The issue view.

Timesheets (Enterprise module)

Teams that bill or approve time can add the Timesheets module. It is built on the same worklogs, so nothing is entered twice. It appears in the top navigation once a licence that includes it is applied; without one the menu entry is hidden and your worklogs keep working as above.

• My timesheet — a week grid with issues as rows and days as columns. Type time into a cell: 1:30, 1.5, 90m, 1h 30m or 2h; a bare number is hours. Enter saves and moves down; arrow keys and Tab move between cells. Add issue adds a row; Copy last week’s rows brings last week’s issues in as empty rows. Totals, the target (default 8 h × Monday–Friday) and the difference are shown for each day and the week. Weeks start on Monday.
• Submit for approval locks the week: nobody — in the grid, on the issue or through the API — can add, change or delete worklogs of that week. You can recall a submission that has not been decided. A rejected week is open again.
• Approvals — approvers see submitted weeks of the people they approve for and press Approve or Reject (a comment is required to reject). Nobody can approve their own week.
• Reports — pick a date range (up to 366 days) and group by user, issue, project, account, team or day. Shows logged, billable and non-billable time, utilisation against the target, and which teams have submitted. Export CSV downloads the table.
• Teams, accounts and rates — an administrator sets up teams with leads and approvers, billing accounts and rates that apply from a given date. New worklogs are billable by default.
• Reminders — people who have not submitted by the deadline get a reminder e-mail.