.webp)
Jira Learns Arithmetic: Capacity Plans, Budgets, and the End of the Side Spreadsheet
Every organization has one. Not a spreadsheet. The spreadsheet. The one where the capacity plan lives, or the project budget, or both. It is maintained by a single heroic person, circulated as an attachment named FINAL_v7, and reliably wrong within a week of being sent. It works beautifully right up until somebody makes a decision based on it.
On August 25, 2026, Atlassian published an announcement whose title reads like a direct shot at that document: “Jira goes where spreadsheets can't”. Behind the headline sit three features—individual capacity planning, formula fields, and space insights—that move the math into the same system as the work. Having read the announcement and the supporting documentation, here is my honest read: this is a genuinely useful release, with fine print worth understanding before you promise anyone a portfolio budget dashboard.
What Atlassian actually shipped
The announcement, written by three Jira product managers, frames the problem exactly the way practitioners live it: the capacity plan, the budget, the status deck, and the actual work all sit in different systems, and keeping them synchronized is a losing game. The proposed fix is to bring planning and reporting into Jira, where the numbers update as the work updates, and where Rovo can see all of it.
Atlassian states that all of these features are available now for Jira Cloud customers, with one plan restriction called out in the announcement itself: individual capacity planning requires a Premium or Enterprise plan, though it works across all space types. If the word “space” still catches your eye, that is the container formerly known as the Jira project, a rename we walked through in our first Jira Spaces explainer. Sharp readers will also remember the Capacity view and formula fields appearing as bullet points in our look at Jira's summer 2026 release. This announcement is Atlassian moving the planning story from the footnotes to the headline.
Three features, one thesis
The Capacity view gives team leads a per-person picture of bandwidth. Per Atlassian's capacity planning guide, allocations come in hours, percentages, or days, with leave, on-call, and keep-the-lights-on work sitting alongside project time, across multiple spaces. Rovo edits the plan in natural language (“Add Jordan to Summer Campaign at 60% through this month”), and it will even import your existing capacity spreadsheet and map the allocations for review. There is something quietly funny about a spreadsheet replacement whose first act is to politely import your spreadsheet.
Formula fields are a new custom field type that runs calculations directly on work items. Budget variance is the flagship example: approved budget minus actual costs, recalculated as work gets logged. Results appear in views and dashboards, are searchable in JQL, and can trigger automations. Describe the outcome you want and Rovo writes the formula, with a Fix formula option for the ones that refuse to validate. Per Atlassian's formula field documentation, outputs cover numbers, text, dates, and durations, with currency and percentage formatting available.
Space insights replace the static status report with a live Reports view in every space: charts in seven styles, lists, smart links, and activity streams. Tell Rovo what you want to see and it builds the chart; select Insights and it explains the trend in plain language. Anyone with access to the space can view and filter the page, while only space admins can change the layout, a small detail your governance team will appreciate.
The fine print worth reading twice
Now the part I suspect many first-day demos will skate past.
First, a formula field can only use data within a single work item. Atlassian's documentation is explicit: a formula on work item A cannot reach into work items B or C. That means no summing actual costs across an epic's children, and no rolling a budget up across a space. Second, space insights display data from one space only; a view that spans spaces still means a classic Jira dashboard. Third, the plan tiers matter beyond capacity planning: some insight metrics and segments are limited to Premium and Enterprise, and chart history runs roughly thirteen months on Standard versus up to three years on Premium.
Read those constraints together and the shape of the release becomes clear. These are team-scale tools, and very good ones. They will answer “is this campaign over budget?” and “is Jordan overloaded?” with less ceremony than anything Jira has offered before. What they are not is a portfolio finance layer. Jira is not becoming your system of financial record, cross-space rollups still belong to Plans and purpose-built tooling, and the executive view that spans ten spaces still gets assembled the way we described in our guide to Jira dashboards executives actually use. None of that is a flaw. It is a scoping decision, and a fact worth knowing before your CFO asks for the cross-project version.
The fields can think now, so govern them like it
Formula fields are business logic living inside field configuration. They feed dashboards, answer JQL queries, and fire automations, which means a wrong formula is not a quiet mistake; it is a wrong number wearing the confidence of every dashboard that references it. Custom field sprawl was already one of the classic Jira governance conversations, and those fields now compute. In company-managed spaces there is an extra wrinkle: a formula field's context is either all spaces or exactly one, with no option to pick a subset, so naming conventions and ownership matter from the very first field you create. Treat formulas the way disciplined teams treat automation rules: named, documented, owned, and reviewed on a schedule.
Capacity plans deserve a similar pause, because they are people data. Individual allocation percentages, leave, and on-call assignments now live inside a work management tool. Before your team leads load all of that in, confirm who can see the plan in your configuration, the same question you would ask about any HR-adjacent data.
And one evergreen truth survives the announcement intact: budget minus actuals is only as live as the actuals people log. The spreadsheet was never really the problem; the update discipline was. Jira just made keeping the numbers current dramatically cheaper. It did not make it automatic.
Who should care, and what to do this quarter
If your marketing, HR, finance, or events teams already run their work in Jira, or you have been looking for a reason to move them off the 47-column spreadsheet, this release plus the new business team templates is that reason. Start deliberately small: one space, one formula field (budget variance is the obvious candidate), one insights dashboard, and one team lead running a real capacity plan for a full cycle. Four weeks of honest use will teach you more than any demo, including Atlassian's.
There is also a strategic reading. Atlassian is candid that capacity plans, budget formulas, and project data feed the Teamwork Graph, the connected data layer that gives Rovo its context, the same architecture thread we pulled on in our read of Atlassian's Q4 FY26 shareholder letter. Every plan and formula you move into Jira makes the AI layer more useful, which is precisely why Atlassian built such generous on-ramps. That is not sinister. It is the strategy, stated out loud.
The Avaratak Take
This release is Atlassian eating the work-about-work spreadsheet layer, one team at a time, and it is a sensible meal. The features are real, shipping, and immediately useful at team scale. Three things I would tell any platform owner this week. Watch the tier line: capacity planning and the richer insight metrics sit on the Premium side, so if you are on Standard, this announcement is quietly part of a Premium business case, and you should price that consciously rather than discover it mid-rollout. Put formula field governance in place before the tenth field exists, not after the two-hundredth. And do not oversell the rollups: know the single-work-item and single-space boundaries cold, because the second question every executive asks after seeing a budget field is “can I see that across everything?”, and the honest answer today involves Plans, dashboards, or patience.
The side spreadsheet is not dead. Its job description just got a lot shorter, and for most teams that is the right trade. If you are working out which of your spreadsheets should make the move first, that is exactly the kind of unglamorous, high-leverage question our senior Atlassian consultants enjoy, and you know where to find us at avaratak.com.