Jira timesheets: a week of time across issues, submitted and approved

Jira has no timesheet page. Calibro Track adds one: a person’s week across every issue they touched, with a total against a target, three ways to fill it in, and a Submit button that hands it to someone who can approve it.

Written 2026-09-09 from the app’s own documentation. Everything here is shipped, not planned.

What a timesheet is here

Open Apps → Calibro Track and you land on your own week. The rail on the left is the week; the panel on the right is the day you have selected.

Week total

Everything logged this week against your weekly target — 40 hours by default, yours to change.

Day rows

Each day’s total and a bar showing it against eight hours. Click one to open it.

Status breakdown

How much of the week is still draft, waiting on an approver, or approved.

Submit week

Sends every draft entry in the week, and the button says how many hours that is. When there is nothing left it reads Nothing to submit.

A timesheet is one person’s. Yours is always your own; an approver sees other people’s weeks in the Approvals queue once they are submitted, and a report grouped by person sees the totals. There is no screen for reading a colleague’s unsubmitted week, and that is intentional.

Filling it in

Typing an entry

The composer at the top of each day takes an issue, a duration and an optional note. The issue search is already in sections before you type: Assigned to you first, then Recently logged — issues you logged against lately whoever they are assigned to, which is how you find yesterday’s ticket when it belongs to someone else — then everything else once you type a key or a few words of the summary.

Durations read the way people write them: 2h30, 1h 30m, 1.5h, 90. Logging on a future date is allowed by default, because putting next week’s planned hours on a timesheet is a normal thing to do with one; an admin can switch that off.

Timing instead of typing

Each day carries a Start beside the composer. The timer runs on the server, one at a time, and follows you around the app as a pill in the header and in the browser tab title. Stopping it writes the entry — the confirm strip that appears afterwards edits an entry that already exists, so a closed tab loses nothing. A timer under a minute writes nothing and pauses instead. Timing your work →

Drawing the week on a calendar

The View switcher has two views, List and Calendar, and they are the same entries — the calendar adds when to the list’s how long. Press on an empty stretch of a day and drag to draw a block, then pick the issue; blocks snap to fifteen minutes. Drag an issue in from the rail and it is logged where you drop it. Drag a block to another time or day, or its bottom edge to change its length. An entry logged without a clock time sits in a strip at the top of its day and counts either way.

Saying it

Press Ask Track and tell the app’s Rovo agent: log 45 minutes on IS-42 for today, pairing on the migration runner. It shows what it will write and waits for you to confirm; the entry appears on the timesheet as it says so. Rovo time tracking →

Submitting the week

Time you log starts as a draft. You can submit one entry, a day, or the whole week; Submit week picks up anything rejected and fixed as well as anything new. An entry a timer left with an open question — Needs a note or Check this — is real time and stays in the day, but it is counted out of every Submit until you settle it, so a week that submits fewer hours than it shows usually has one of those in it.

A submitted entry can be recalled at any point before someone decides on it. Approved entries lock; an approver can reopen one. The approver’s side of this is on the approvals page.

After the week is approved

Approved hours are what the reports and the payroll export count by default. A report grouped by person and filtered to approved time is the timesheet summary most teams want on a Monday; the payroll export turns the same hours into a CSV in the shape ADP, Gusto, Paychex, Workday, QuickBooks or Rippling already imports, with the run screen naming anyone whose week is not approved yet. Building a report →

A timesheet is not Jira’s work log

Calibro Track keeps its own entries and never modifies the work log on your issues, so uninstalling changes nothing in Jira — and, equally, hours logged in Track do not appear in Jira’s Time Spent field. Time entries, approvals and saved reports live in Forge storage attached to your site and are processed inside Atlassian’s infrastructure; there is no Calibro server holding a copy. Any report exports every entry to CSV, and you should do that before uninstalling, because uninstalling deletes the data.

In your language

The whole app — timesheets, approvals, reports, settings and the payroll export — is in English, German, Spanish, French and Portuguese (Brazil), following each person’s own Atlassian language with nothing to configure. Week start and date format come from the same place.