Overview Back to top

The Time Tracking module lets you log work hours against any Jira issue or custom allocation created on the Resource Scheduler. Each entry is called a worklog — it records the issue or allocation, the date, the number of hours, and an optional description.

Time Tracking weekly grid view showing issues as rows and days as columns

Key Features

  • Weekly grid: Days as columns, issues as rows, hours in cells
  • Quick logging: Click "+ Log Work" to record time with quick-select buttons
  • Live Start / Stop timer: Run a real-time counter against any Jira issue and let WorkHub fill in the duration on stop
  • Jira issue panel: A collapsible WorkHub panel on every Jira issue view with Log time, Start timer, and the full worklog history
  • Date-range filters: Today, This Week, Last Week, This Month, Last Month, or Custom
  • Excel export: Download worklogs matching the current filter
  • Timesheet integration: Worklogs feed into the approval workflow

Logging a Worklog Back to top

Click the + Log Work button in the toolbar to open the worklog form. Fill in the fields below and click Save.

Field Details
Issue Search and select a Jira issue. Type at least two characters to search across all projects — the picker matches issue key and summary. Custom allocations are not returned by this search; to log time on an allocation, click its cell directly on the weekly grid (see below).
Time Spent Enter hours and minutes. Use the quick-select buttons (15m, 30m, 45m, 1h, 2h, 4h, 6h, 8h) for common durations. You can log only minutes, only hours, or both.
Date The day the work was done. Defaults to today.
Description Optional text describing what was done. Useful for timesheet reviews and audits.
Log Work dialog showing issue picker, time spent input with quick-select buttons, date selector, and description field
  1. Click "+ Log Work" — open the form from the toolbar at the top of the Time Tracking view.
  2. Pick an issue — type in the Issue field to search by key or summary. Select the issue you worked on from the dropdown.
  3. Set time spent — enter hours and minutes, or use the quick-select buttons for common durations.
  4. Choose date — pick the date the work was done. Defaults to today.
  5. Add a description (optional) — describe what you accomplished. This text shows up in the grid view and in exports.
  6. Save — click Save. The new worklog appears immediately in the weekly grid.

Logging work against allocations

Worklogs can also be logged against custom allocations — non-issue work such as training, meetings, or support rotation that was scheduled for you on the Resource Scheduler. Allocations are not available in the issue search inside the Log Work dialog. Instead, every allocation assigned to you appears as its own dedicated row on the Time Tracking weekly grid for the dates it covers, and you log work against it from there.

There are two ways to log time on an allocation:

  1. From Time Tracking — on the weekly grid, allocations show up as rows under your issue rows (marked with an allocation badge). Click any cell on an allocation row that falls within its scheduled date range to open the Log Work dialog with that allocation already pre-selected. There is no item search in this case — the target is fixed to the allocation you clicked, and you only fill in time spent, date, and description.
  2. From the Scheduler — right-click on an allocation bar (or on a cell on your own row) and choose Log Work. The dialog opens with the allocation pre-selected, exactly the same as from the grid.
Why allocations don't appear in the issue search

Allocations are personal scheduled work, not Jira issues, so they are surfaced contextually on the rows where they apply rather than mixed into a global issue picker. Allocation worklogs still flow into timesheets and reports just like issue worklogs.

Note: If an allocation's category has work logging disabled by an admin, the allocation row appears on the grid but its cells are not clickable, and the row is labelled accordingly. Ask your admin to enable work logging on the category if you need to track time against it.

Start / Stop Timer Back to top

Run a live timer while you work and WorkHub fills in the hours when you stop. Available from the Time Tracking toolbar and the WorkHub panel on any Jira issue.

Time Tracking toolbar with the Start timer button

Start

Click Start timer. Pick an issue from the list of recents, or type to search. The timer begins immediately.

Issue picker for the timer

Stop

The button turns orange and shows the live elapsed time. Click it to stop — the Log Work dialog opens pre-filled with the issue and duration so you can adjust and save.

Stop timer button showing elapsed time

One timer at a time

Starting a new timer while another is running shows a confirmation. Confirm to log the previous timer's elapsed time and switch to the new issue.

Confirmation when replacing a running timer

Jira Issue Panel Back to top

WorkHub adds a panel on the right side of every Jira issue. Log time, run the timer, and see the full worklog history without leaving the issue.

WorkHub panel on a Jira issue

Scheduled-for date

Shows the start and end date for the issue, taken from the fields admins map under Settings. If no date fields are mapped or the issue has none set, the panel says so instead.

Log time

Click Log time to expand an inline form with description, date, hours and minutes — faster than the full dialog when you just need to record a quick entry.

Timer

Same timer as the Time Tracking toolbar. Stopping it from the panel opens the inline log form instead of the full dialog.

Worklog history

Every worklog on the issue, by anyone. The TOTAL at the top sums them up.

Weekly Grid View Back to top

The weekly grid is the primary layout for time tracking. Issues appear as rows, days of the week as columns, and hours are displayed in cells at the intersection.

  • Each issue row represents a Jira issue you have logged time against.
  • Each allocation row represents a custom allocation scheduled for you on the Resource Scheduler; the row is marked with an allocation badge and only shows clickable cells on the dates the allocation covers.
  • Each "Out of period" allocation row appears when you have worklogs against an allocation that no longer covers the visible week — either because the allocation was deleted (worklogs are preserved for historical reporting) or because it was rescheduled to a different date range. The row is dimmed, labelled Out of period, and read-only: cells with hours are clickable so you can review or delete those worklogs, but you cannot log new time against an absent allocation.
  • Each column represents a day of the week (Monday through Sunday).
  • Each cell shows the hours logged for that issue or allocation on that day.
  • Row totals show the sum of hours for each issue or allocation across the week.
  • Column totals show the sum of hours for each day across all rows — including any "Out of period" allocation hours, so the per-day total always matches the sum of every visible row.
  • Week navigation arrows let you move to the previous or next week.
Weekly grid showing issues as rows, weekdays as columns, and hour totals
Tip: Click any cell in the grid to quickly add or edit a worklog for that issue and day. Use the week navigation arrows or the date picker to move between weeks.
Stack view: Use the view-mode toggle in the toolbar to switch from the table layout to Stack view, which lays each day out as a column of cards — one card per worklog. Both Jira-issue worklogs and allocation worklogs appear in stack view, so the per-day count and totals match the table view.

"Out of period" allocation rows

When you have worklogs against an allocation that no longer covers the visible week — either because the allocation was deleted (worklogs are preserved for historical reporting) or because it was rescheduled to a different date range — the grid shows a synthetic Out of period row so the per-day Total cells always tie back to a visible row. The row is dimmed and read-only: cells with hours are clickable to review or delete the historic entries, but you cannot log new time against an absent allocation.

Time Tracking weekly grid showing two Out of period allocation rows below the user row, each dimmed and labelled in red

Date Range Filters Back to top

Use the date-range selector in the toolbar to control which worklogs appear in the grid.

Predefined ranges

  • Today — worklogs for the current day only.
  • This Week — Monday to Sunday of the current week.
  • Last Week — the previous full week.
  • This Month — first to last day of the current month.
  • Last Month — the previous full calendar month.

Custom range

Open the period dropdown and choose Custom Range... at the bottom. From / To date inputs expand inline; pick the start and end dates and press Apply. The grid renders one column per day across the selected range (up to 366 days). The chosen range is remembered across page refreshes; the prev / next arrows shift it by the same length. To edit the range, reopen the dropdown and click Custom Range... again — your previous From / To values are pre-filled.

Custom ranges are useful for billing cycles, sprints, or any period that does not match the presets. To return to a standard period, pick Current Week, Last Week, Last 2 Weeks, Current Month, or Last Month from the same dropdown.

Editing & Deleting Back to top

You can change or remove any worklog as long as it is not part of a submitted or approved timesheet.

Editing

  1. Click any cell in the grid with logged hours to open the day worklogs dialog — a list of every entry for that issue (or allocation) and date.
  2. Click the pencil icon on the worklog row you want to change. The Hours and Description cells turn into inputs.
  3. Update the hours (decimal allowed, e.g. 1.5 for 1h 30m) and description, then click the green tick to save or the cross to cancel.

Edits stay inside the time tracking grid — there is no need to open the parent issue. The change is saved through the same backend resolvers that gate worklog locking, so any attempt to edit a worklog inside a submitted/approved timesheet period is blocked with a clear error.

Deleting

  1. Click the delete icon on the worklog entry.
  2. Confirm the deletion in the dialog that appears.
  3. The worklog is permanently removed.

Locked worklogs

Worklogs that belong to a submitted or approved timesheet cannot be edited or deleted. The entry shows a lock icon and the controls are disabled. To make changes, ask your approver to reject or reopen the timesheet first. See Timesheets & Approval for details.

Excel Export Back to top

Click the Export button in the toolbar to download your worklogs as an Excel file. The export includes every worklog that matches the current date-range filter.

Columns in the export

Column Content
Issue KeyJira issue key (e.g. WH-123)
Issue SummarySummary text of the Jira issue
ProjectJira project the issue belongs to
UserFull name of the team member
DateDate the work was done (YYYY-MM-DD)
HoursHours logged
DescriptionWork description text
Common export uses:
  • Personal records — export "This Month" for a quick hours summary.
  • Client invoicing — filter by a project and export the billing period.
  • Audits — export a custom date range for internal or external review.

Need Help?

If you have questions or need assistance with time tracking in WorkHub for Jira, our support team is here to help.

Contact Support