Know what a project costs before finance asks.
Cost comes from the hours already logged in Jira, priced at the rate that applied on the day. Earned value tells you whether that spend bought the progress it should have — and health weighs cost and schedule together.
The real module, running right here.
Working software on sample data — the same interface that renders inside Jira. It plays a short tour when it comes into view; click anywhere in it to take over.
Three sample budgets on made-up hours. Change a rate or drag the story points, and cost, earned value, forecast and health move the way they do in the app. Installed in Jira, cost comes from your real worklogs.
Built for the job, not the brochure.
Budgets with shape
A budget per project with start and end dates, lines for what the money is for, and its own currency.
Cost from worklogs
Each worklog is priced at the rate that applied on the day the work happened — the person’s own rate first, then the project’s, then the site default.
Earned value, honestly
Planned value, earned value and actual cost, with CPI, SPI, a forecast at completion and the performance you’d need to finish on budget.
Health that isn’t fooled
A project that has spent little but is far behind is not “on track”. Health checks cost and schedule separately and says which one is slipping.
Revenue and margin
Billable rates turn billable hours into revenue, so margin sits next to cost on the same page.
Rates stay private
Only Jira admins set rates. Budget owners see rates and per-person cost; managers see spend and health, not salaries.
Three steps from install to answer.
Set rates once
A default for the site, overrides per project and per person, each with the date it starts.
Create the budget
Dates, lines and a currency, plus the issues it covers. Percent complete comes from you, story points or resolved issues.
Watch it move
As hours are logged, cost, earned value, forecast and health update — and correcting a rate reprices the work it covers.
Inside Atlassian, with Jira’s rules.
Cost is never stored. It is worked out from worklogs and rates each time, so a corrected rate reprices the work it covers, and nothing about pay leaves Atlassian’s boundary. What “never leaves your instance” means →
- Percent complete comes from a figure the owner sets, then resolved story points, then resolved issues — never elapsed time
- No forecast is shown until 10% of the budget is spent, so three logged hours can’t predict the whole project
- Per-person cost appears only for budget owners allowed to see those people’s hours
- Rates can be set only by Jira administrators
Straight answers.
How is project cost worked out?
From the hours logged in Jira. Each worklog is priced at the hourly rate that applied on the day the work happened — the person’s own rate first, then the project’s, then the site-wide default. Cost is never stored, so correcting a rate reprices the work it covers.
Why doesn’t my new budget show a forecast yet?
A forecast at completion divides the budget by the cost performance index, and early on that index is noise: a handful of hours against a large budget can suggest the whole project will cost almost nothing. The app waits until 10% of the budget is spent.
Where does percent complete come from?
A figure the budget owner sets, if there is one. Otherwise resolved story points out of the total, and if the issues have no points, resolved issues out of the total. Elapsed time is deliberately not used, because it makes a late project look on schedule.
Guides and articles.
Earned value for Jira projects, in plain English
Spent 48% of the budget — is that good? Earned value answers by comparing what you spent with what that money was supposed to buy. Here is the whole idea, with one worked example.
Read the guide →Turn a support address into Jira issues with Cloudflare Email Routing
Forward a support address on your own domain into Jira, so each new message becomes an issue and each reply lands as a comment — without giving any app a mailbox.
Read the guide →See Claude Code spend per person, team and Jira issue
Point Claude Code’s own telemetry and a GitHub webhook at Workforce Intelligence, and see what AI coding costs — per person, per team, and per Jira issue it helped build.
Read the guide →Be first in when it opens.
One email when early access opens. Nothing else — no newsletter, no drip sequence, and the list isn't shared with anyone.
Early access members get the first year at launch pricing, locked.
Your address is stored with Resend, the email service that will send that one email.