"The project is at 85% of budget with a month to go. Which part of it went over?" If you run client or internal work in Jira, you have probably been asked this, and the honest answer is often a spreadsheet you build that afternoon.
I'm Marcin, founder of Radrly, and we build MarginRadar, a budget and margin app for Jira Cloud. Below are the questions I hear most about cost per epic, answered with native Jira first. Our app comes in near the end.
Can Jira show time spent per epic?
Partly. The Σ Time Spent field rolls up one level: a sub-task's time shows on its parent story, and a story's own time shows on the epic, yet the sub-task hours under that story never reach the epic. This is tracked as JRACLOUD-70150, which Atlassian last updated in June 2025 with Automation as the suggested workaround.
What does the Automation workaround look like?
A rule on the epic uses the Lookup work items action with JQL such as parent = {{issue.key}}, then writes a sum into a number field on the epic with a smart value like {{lookupIssues.customfield_10050.sum}}. Atlassian's knowledge base article on summing story points to the parent shows the pattern with story points; the same works for a number field that holds hours.
Run it on a schedule or when a worklog changes. Expect to tune it. Lookups have result limits, and you need one more level of lookup if sub-tasks sit under the stories.
That gives hours. How do I get money?
Jira has no cost rates, so money means a spreadsheet: export the worklogs, map each person to a rate, multiply, and pivot by epic. It works for a month end review. It goes stale the next day, and the rates live in a file that has to be kept away from the wider team.
Can I set a budget on an epic natively?
You can add a number field called Budget and compare it with the rolled up hours in a filter or a dashboard. There is no threshold, no alert and no money unless you convert hours by hand.
So what does MarginRadar add?
MarginRadar calculates cost from native Jira worklogs multiplied by rate cards (by role, by person or per space).
On Standard, the period report on the space's Report tab groups cost, billable value, hours and expenses By epic, for this month, last month, this quarter or a custom range. Hours on sub-tasks land on the epic above their story. On an epic, the MarginRadar panel totals cost, hours, billable value and margin for everything beneath it, or for the epic alone if you untick Epic + subtasks. That already answers "which epic went over" after the fact.
On Advanced, the Epic risk card on the space page lets you give an epic its own budget with Add epic budget. Every worklog below the epic counts towards it, sub-tasks of its stories included, and each epic shows spent against budget with a status.
Epic risk card (Advanced): budget, spent and status per epic, from worklogs on child work items.
What happens when an epic crosses a threshold? Every budget has a warning and a critical threshold (80% and 100% by default), and on both editions the space page and the work item panel show where it stands. Alerts are Advanced: the Alerts tab on the space page lists each crossing without money amounts. MarginRadar also posts a Jira comment on the epic, and that comment always includes money. Anyone who can see the epic can read it, so check the space's audience before you turn it on.
Can it tell me where the space will land? The forecast is Advanced. It takes the cost of the last 14 days, turns it into a daily burn rate and projects it to the budget end date as Estimate at completion. A hybrid forecast adds a P50 to P90 range for the run out date.
Forecast (Advanced): run out date and estimate at completion for the space budget.
Who sees the money? Three roles. Finance sees everything. PMs see cost, billable value and margin but not the per person breakdown. Viewers see status and percentages only.
Honest limits
- A worklog is assigned to its epic when MarginRadar first sees it. If you move a story to a different epic, run Import worklogs again so its earlier hours follow it.
- The numbers are only as good as the worklogs. Time tracked in a separate app counts only once it syncs to Jira worklogs.
- One base currency per site, and no exchange rates fetched.
- MarginRadar is a budget and margin view for delivery teams. Your accounting system stays where it is.
Listing: MarginRadar on the Atlassian Marketplace.
How do you answer "which epic went over" today: an Automation roll up, a spreadsheet, or a report from another tool?