Field Notes
Essays from inside a 120-person digital agency on Jira — written by Ernest. Project margin, estimating, the architecture of profitability, and the small decisions that compound. No content marketing.
Finance needs to read Jira — worklogs, estimates, project structure — but a CFO with a Jira admin account is the wrong answer to the right question. How agencies give finance a real view of delivery data: scoped accounts, dashboards, and a financial layer where every role reads the same numbers in the unit that fits their job.
The delivery experience of Jira Cloud and Jira Data Center is nearly identical. The finance experience isn't. Authentication, worklog APIs, data residency and plugin economics all differ — and they decide which financial tooling your agency can actually run. A practical comparison for agency CTOs and finance leads.
Jira projects are organised for delivery — one key per client, per team, per product. Your P&L is organised by contract. The two almost never line up, which is why agencies with perfect worklogs still can't answer what a specific engagement earned. Here is the mapping layer that fixes it.
Every margin number is downstream of the worklogs, and worklogs go wrong for predictable reasons — most of them incentives, not laziness. Six steps to time data you can trust: what to ask for, what to stop rewarding, and why surveillance produces worse numbers, not better ones.
Most financial tools that integrate with Jira do so with read-write permission. Some of them write back. Some of them install plugins inside Jira itself. Some of them require an admin account to be shared with the vendor. Each of those decisions has a security and operational cost that does not appear on the procurement page. The tools that connect read-only and own no Jira state are a smaller, quieter category — and the one a CTO should be asking for.
A practical setup guide for agencies that want to read margin out of Jira without forcing engineers to change how they work. Sub-project structure with components, role tagging, three custom fields, and the JQL hooks that make it all queryable.
Four JQL queries that tell a finance director more about project health than any closing pack: hours-without-cost, role drift, sub-project drift, and stalled worklogs. The exact JQL, what each query reveals, and the action it should trigger.
15 minutes on your real Jira, our screen.
Book a demoMost financial plugins on the Atlassian Marketplace cannot read worklogs on their own — they require a companion time-tracking plugin to be installed and used by every hour-logger on your team. The architecture is rarely on the marketing page. The TCO is rarely calculated until month four.