Skip to content

Atlassian Marketplace app for Jira Cloud

Budget tracking and cost reports for Jira.

OnBudget is a Jira Cloud app for budget tracking and cost reporting. It turns work you already track in Jira into money. Pick story points, worklogs with rate cards, a numeric field, or counts of work items, set a budget in one of 18 currencies, and get spend, variance, and a forecast on your dashboard. Built on Forge. Read only.

Install from the Atlassian Marketplace See how a report is built
Nine budgets across delivery, product and marketing, each showing spend against budget, forecast, and whether it is on track, at risk or over.
  • Runs on Atlassian
  • Built on Forge
  • Read only access
  • Stores only report settings
  • No new custom fields

The gap

Jira knows what happened. It does not know what it cost.

The work is already in Jira. The money is in a spreadsheet somebody exports on Fridays, and by Monday it is wrong. Teams that do not use story points or timesheets, which is most of marketing, support and operations, do not appear in that spreadsheet at all.

  • Are we over budget on this epic, right now?
  • What did that release actually cost us?
  • At this burn rate, when do we run out?
A report that has gone over: 106 percent of budget consumed, a negative remaining balance, and a forecast well past the line.
A report that has gone over: 106 percent of budget consumed, a negative remaining balance, and a forecast well past the line.

How it works

Four steps from a Jira space to a budget you can defend.

  1. 01

    Choose where the numbers come from

    Point a report at whole spaces, at individual work items picked by key, prefix or summary text, or at a JQL query that is validated as you type. One toggle pulls in sub-tasks and everything under an epic.

    Step one of the builder: point the report at spaces, at individual work items, or at a JQL query, and decide whether to pull in everything under an epic.

  2. 02

    Set the budget, the currency and the two thresholds

    A total budget in any of 18 currencies, plus the two percentages that decide when a report turns amber and when it turns red. Number, decimal and date formats are set per report, so a Brazilian budget reads like one.

    Step two: a total budget in one of 18 currencies, the two thresholds that turn the report amber and red, and per-report number and date formats.

  3. 03

    Pick the signal your team already has

    Five costing methods, and OnBudget samples your data first and tells you what share of your work items actually carries each one before you commit to it.

    Each costing method shows how much of your data actually carries it, 14 percent, 38 percent and 47 percent here, before you commit to one.

  4. 04

    Add a time frame and a forecast horizon

    Limit the report to a date range, then forecast to the end date, to 30, 60 or 90 days out, or not at all. Preview the whole thing before you save it.

    The preview step, before anything is saved. Regenerate until the numbers look right, then save the report.

Costing

Pick the signal your team already has.

The hard part of costing Jira work is not the arithmetic. It is that every team measures something different, and half of them measure nothing at all. OnBudget samples your data and shows you what share of your work items carries each signal, before you build anything on top of it.

Five ways to turn work into money

Each method shows its coverage across your data before you commit to it.

  • Story points, priced per point
  • A numeric field, priced per unit
  • Worklogs, priced by rate card or a flat rate
  • Work items closed or resolved, priced per item
  • Work items sitting in chosen statuses, priced per item

Rate cards for logged time

For teams that bill or cost time rather than estimate it.

  • Rates per user or per project role
  • A fallback hourly rate when no entry matches the author
  • Role members resolved by user, group or project role
  • Reusable worklog role presets, defined by project admins
  • Hour, day, thirty minute or fifteen minute time basis
Each costing method shows how much of your data actually carries it, 14 percent, 38 percent and 47 percent here, before you commit to one.
Each costing method shows how much of your data actually carries it, 14 percent, 38 percent and 47 percent here, before you commit to one.

Dashboards

The dashboard is yours to rearrange.

Nine gadget types, each with its own chart formats. Drag one to a new slot, resize it from the corner, clone it, remove it, or switch it between bar, line, area, pie, donut, table and plain number. Save the layout when it reads the way you think.

  • Insights
  • Budget summary
  • Budget health gauge
  • Planned versus actual
  • Spend over time
  • Forecast versus end date
  • Variance
  • Breakdown by status, assignee, space or type
  • Compare reports
A report at 83 percent of budget: summary, health gauge, planned versus actual, spend over time, and spend by status.
A report at 83 percent of budget: summary, health gauge, planned versus actual, spend over time, and spend by status.
Edit mode. Drag a gadget to a new slot, resize it from the corner, clone or remove it, switch its chart format, then save the layout.
Edit mode. Drag a gadget to a new slot, resize it from the corner, clone or remove it, switch its chart format, then save the layout.

Sharing

A shared report respects the reader, not the author.

Most reporting tools hand out a snapshot of what the author could see. OnBudget does not. When someone opens a report you shared with them, it is regenerated under their own Jira permissions, so nobody sees work items they could not already open in Jira. If a viewer lacks access to part of the scope, the report says so rather than quietly showing a smaller number.

Table view listing every budget with its method and origin, and below it the reports other people have shared with you.

At scale

Built for the hundredth report, not the first.

A budgeting tool is easy to like with three reports open and hard to live with at fifty. This is what the app gives you once a portfolio has grown.

  • Cards, list and table views
  • Search, and sorting by risk, budget used, forecast variance or recency
  • Filters by health and by currency
  • Favourites, hiding, and bulk star, hide or delete
  • Sharing with users or groups, regenerated under each viewer's permissions
  • CSV export, generated in your browser
Select several reports and act on all of them at once: star, hide or delete.
Searching the portfolio down to one team's budgets.

Security and data

Read only, and it stays inside Atlassian.

OnBudget stores your report settings and nothing else. It never stores the content of your work items, and it never stores the results of a report. Every read is made with your own Jira permissions, account and group identifiers are hashed before they are used as storage keys, and uninstalling the app purges everything it held.

Requested permissions

  • read:jira-work
  • read:jira-user
  • storage:app

Languages

It speaks the language your team reports in.

The whole interface is available in English, Portuguese and Spanish, and each report carries its own currency, number format and date format. A budget in reais reads like a budget in reais, not like a US spreadsheet with the wrong separators.

Questions

Things people ask before they install it.

Does OnBudget need me to create custom fields in Jira?
No. OnBudget reads what is already there: story points, worklogs, existing numeric fields, statuses and resolutions. There is nothing to add to a screen scheme and nothing to backfill, which is why a first report takes minutes rather than a change request.
What can OnBudget use to calculate cost?
Five signals. Story points priced per point, any numeric field priced per unit, worklogs priced by a rate card or a flat rate, work items closed or resolved priced per item, and work items sitting in chosen statuses priced per item. You can also leave the unit cost blank and let OnBudget divide the total budget across the total quantity.
How does OnBudget know what an hour of work costs?
Through rate cards. A card holds rates per user or per project role, plus a fallback hourly rate for authors it does not recognise. Project admins can define reusable worklog role presets from the project settings, so the same roles do not have to be rebuilt for every report.
What if my team does not use story points or worklogs?
Then count work items instead. OnBudget can price items closed or resolved, or items sitting in statuses you choose. This is the common case for marketing, support and operations, and the builder tells you what share of your data carries each signal before you pick one.
Which currencies are supported, and does OnBudget convert between them?
Eighteen ISO currencies, including USD, EUR, GBP and BRL. Each report is denominated in one currency and OnBudget does not convert between them, because an invented exchange rate is worse than no exchange rate. Number, decimal and date formats are set per report alongside it.
Can I share a report with someone who has limited Jira access?
Yes, with users or with groups. A shared report is not a snapshot of your view. It regenerates under the viewer's own Jira permissions, so nobody sees work items they could not already see in Jira, and the report warns when a viewer lacks access to part of its scope.
Where does my data live?
Inside Atlassian. OnBudget runs entirely on Forge, is Runs on Atlassian, and holds three read-only scopes. It stores your report settings and never the content of your work items or the results of a report. Account and group identifiers are hashed before use as storage keys, and uninstalling purges everything.
Can I export the numbers?
Yes, as CSV with the per work item breakdown behind the totals. The file is generated in your browser, so the data does not leave Atlassian to produce it.
What is the difference between at risk and over budget?
Two percentages you set per report. At risk defaults to 80 percent of budget consumed and over budget to 100 percent. They drive the health lozenge, the colour of the gauge, and the sort order on the home screen, so the reports that need attention rise to the top.
How far ahead does the forecast go?
As far as you choose: to the report's end date, or 30, 60 or 90 days from today. You can also turn the forecast off. The projection is a linear run rate from the spend recorded so far, shown against the budget so any overrun or headroom is visible.
Can I see the work behind a number?
Yes. Every report carries a parameters row spelling out the exact scope, method and currency it used, and clicking a bar or slice in a breakdown opens the matching work items in Jira.
Is there a free version?
OnBudget is a paid app with a free trial, sold through the Atlassian Marketplace. See the listing for current pricing, which is where it stays accurate.

Install it, or ask a question first.

It is on the Atlassian Marketplace with a free trial, and the current pricing lives there. If you would rather talk it through, we answer in English, Portuguese and Spanish.

Install from the Atlassian Marketplace Ask us a question

Also from us

The rest of what we make.

See all our apps