Jira time tracking for agencies: what's built in, what isn't

Written by the developer of Worklog Ledger. The goal of this page is to save you a Marketplace subscription you might not need — and to be honest about when you do need one.

Agencies adopting Jira for client work usually assume time tracking is a solved problem — it's a project management tool, after all. The truth is more specific: Jira is good at capturing time and bad at doing anything financial with it. Here's the exact line.

What native Jira time tracking gives you

• Worklogs on every issue. Anyone can log time (duration, start time, a comment) on any issue — the "Log work" action. Entries are per-person and timestamped.
• Estimates and remaining time. Original estimate vs. time spent vs. remaining, visible on the issue and burned down in sprints.
• The Time Tracking report. Per-project, per-version aggregate of estimates vs. logged time — useful for delivery health, not billing.
• JQL's worklogDate and worklogAuthor. You can find issues that someone logged time on in a date range.
• A REST API that exposes everything. Every worklog entry is retrievable programmatically — this is the escape hatch all the tools build on.

Where it stops

• No entry-level reporting. JQL filters issues, not entries. "All hours logged in March, per person, per client" doesn't exist in the UI.
• No worklog export. Issue search exports lifetime "Time Spent" per issue — not the entries, not sliced by your date range.
• No concept of a client. Projects, components and labels exist; "which client pays for this" doesn't. You end up encoding it in project naming conventions.
• No rates, no billable flag. Nothing in Jira knows an hour of senior time costs more than an hour of standups — or that standups aren't billed at all.
• No timesheet view. There's no "my week" grid to review or fill; logging happens issue by issue, which is why entries are chronically missing.

The pragmatic setup for a billing agency

1. Make logging cheap. Unlogged hours are unbilled hours — the biggest leak isn't your tooling, it's Thursday's forgotten afternoon. Whatever you adopt, the weekly calendar view (see, gap, fill) beats issue-by-issue logging.

2. Map projects to clients once. One Jira project per client engagement is the cleanest convention; the mapping then lives in whatever reporting layer you choose, not in people's heads.

3. Add a reporting layer only for the people who bill. This is where the options split by admin rights and budget — Marketplace timesheet apps (site-wide install, per-user pricing) vs. API scripts vs. browser extensions. We compared them honestly in this guide, and if you just need a one-time export there's a working script here.

Disclosure again: we built Worklog Ledger for exactly this setup — a free weekly worklog calendar that makes logging cheap, plus a billing layer (client mapping, rates, invoice-ready CSV) priced per reporting seat instead of per Jira user, installed as a browser extension so there's nothing for a Jira admin to approve.