A typical client deal rarely has one billing shape. Discovery is a fixed fee, the build runs Time and Materials, and support sits on a monthly retainer. The work still lands in one Jira space. The question is how you mark each deliverable, read hours against it, and bring money and revenue modes in.
I'm Marcin, founder of Radrly. We build MarginRadar, a Forge app that turns Jira Cloud worklogs into cost, budget and margin. This article starts with native Jira for splitting one client's work into deliverables, then what MarginRadar adds when the same deal mixes billing models. Advanced-only features are labelled (Advanced).
Mark the deliverables in native Jira
Jira does not know about fixed fees, retainers or billable rates. It does let you group work so each deliverable has a stable handle you can filter on.
Epics. An epic is a larger body of work that spans several sprints. Put discovery, build and support under separate epics (Manage epics in team-managed spaces).
Versions. A version is a set of features and fixes released together. Use versions when a deliverable lines up with a release, then filter with fixVersion (Configure versions in a scrum space).
Components. Components group work items around features, departments or workstreams. They suit a long-running stream such as support.
Labels. Labels are open tags on the work item (How to create and use labels in Jira Cloud). They work for a deal code shared across spaces, with the caveat that anyone can invent a new spelling.
Pick one primary axis per deal and stick to it.
Hours against each deliverable
Native time tracking covers estimates and spent time (Configure time tracking, Log time on a work item): Original Estimate, Remaining Estimate and Time Spent. Each worklog belongs to one work item.
Useful filters look like space = ACME AND parent = ACME-12, fixVersion = "2026-Q1 build", component = Support, or labels = "acme-retainer". JQL fields lists those fields. Save each query as a filter and pin it to a dashboard with Time Spent and Original Estimate columns.
Σ Time Spent, Σ Original Estimate and Σ Remaining Estimate roll up one level only. A story includes its sub-tasks; an epic includes its stories and leaves out the sub-tasks under those stories. For a deliverable total, sum plain Time Spent on the filtered list, or use Automation to look up matching work items and store the sum in a number field. Lookups are capped at 100 work items (Automation service limits), and the number is only as fresh as the last run.
None of this is money. Jira has no rates, no revenue mode and no included retainer hours. The commercial model lives in a spreadsheet or a contract PDF.
What MarginRadar adds
MarginRadar reads native Jira worklogs and multiplies them by rate cards (cost and billable rates for roles, people or a space default). Every rate has an effective date, so a worklog is costed at the rate valid on the day it was logged.
Space budget (Standard). One space has one space-level budget. Units can be money, hours or both. On Standard the revenue mode is billable rates (Time and Materials via the rate cards) or none. The space page shows spent, remaining, burn and margin.
Clients (Standard). Admin > Clients holds reusable client labels. Each space budget can carry one client key, and Portfolio can filter or group by client. Clients are labels for reporting, not a CRM or billing module.
Epic budgets and scoped budgets (Advanced). Advanced adds a budget per epic, and scoped budgets that take a version, label, component or custom JQL. Every scope is AND'd with the current space. Scoped budgets track spend against their own money and hours limits.
Fixed fee and retainer (Advanced). Advanced also adds fixed fee, and retainer (monthly fee, included hours, overage rate, optional hour rollover) on the space budget. Billing periods follow the billing day and timezone. Space budgets can have start and end dates and do not reset each month. The period report still covers this month, last month and this quarter.
Forecast (Advanced). Burn forecast gives a run-out date and an estimate at completion when an end date is set. Hybrid forecast combines recent burn with remaining estimates on open work and shows a P50 to P90 run-out range.
Modelling a mixed deal in one space
Revenue mode is set on the space budget, so a space has one commercial shape at a time. For a mixed deal in one space, set fixed fee or retainer at the space level when that is the headline model, and track the other deliverables with epic or scoped budgets. Epic margin always compares cost to billable rates. If each part needs its own revenue mode, put each part in its own space and share a client label across them.
A practical pattern: one space, client ACME, retainer or fixed fee as the space revenue mode, an epic budget for discovery, a version-scoped budget for the build, and a component-scoped budget for support.
Honest limits
- No invoice generation. Exports are CSV, PDF (print or Save as PDF) and Markdown. Coming soon: an invoice-ready export per billing period, by client and deliverable.
- No resource scheduler and no capacity planner.
- One space-level budget per space. Several deliverables means epic budgets or scoped budgets (Advanced), or separate spaces.
- Revenue mode lives on the space budget. A mixed model in one space is space-level fixed fee or retainer plus scoped or epic budgets for the other parts; it is not three independent revenue modes on one space. Coming soon: a separate revenue mode for each epic and scoped budget.
- Tempo and other trackers are not read directly. Their time counts once it lands in native Jira worklogs.
- Figures live in the app. They are not Jira fields, so you cannot search them in JQL. Coming soon: optional mapping of budget status to a Jira field for JQL and Automation.
Listing: MarginRadar on the Atlassian Marketplace.
How do you split a mixed client deal in Jira today: one space with labels and filters, separate spaces per billing shape, or something else?