Jira Formula Fields at the work item level are here! As part of Atlassian Jira Summer Releases 2026, this feature allows you to calculate metrics at that level. At the same time, there are ways to do it beyond just individual tasks, toward project-level KPIs, portfolio data, and operational intelligence. Discover the key differences between these two layers of calculation, and how to get the best of them: How Jira Formula Fields enhance execution for work items, and how Projectrak's Formula Fields for projects extend that intelligence to projects and portfolio level, enabling better decision-making for projects.
A project manager who opens Jira on a Monday, right before a team project portfolio meeting, and one of the reviewed projects has more than a hundred work items, some finished, others blocked, others waiting for QA… each of those work items tells a detailed story. However, management usually asks for a holistic view of the whole, not specifics, such as budget, time, estimated work, etc. Are two different perspectives on the same work.
At the beginning of 2026, Atlassian announced a seasonal release cycle instead of those constantly weekly and unpredictable releases. As part of the Atlassian Jira 2026 Summer Release, native Jira Formula Fields for work items were introduced. A formula field at this level allows you to calculate different values of interest using information available in a particular work item, and its results can be used in Jira lists, for example.
This release from Jira solves an operational problem but still doesn’t make that Monday problem disappear (the one we mentioned at the beginning). Sometimes the calculation needed isn’t about just a work item, but it’s about the project on top of all those work items, in the case you’re just using Jira.
Imagine a finance-related work item with two fields:
A Jira Formula Field allows you to calculate the difference and show what the Budget Variance is, right there in the same work item (which is $7,000, in the case you were asking)
What’s budget variance and how to calculate it? >>
The same can occur if you’re interested in calculating product prioritization: Imagine a product team wants to calculate a score using Reach, Impact, Confidence, and Effort. This would be simple to calculate by getting the number of days remaining until a deadline, and another team can calculate a risk or a cost metric.
Having Jira Formula Fields at the work item level leaves the calculations close to the operational data.
This alleviates the need to manually calculate values by supporting mathematical, text, logical, date, and time operations, depending on the inputs and outputs required.
This is more than just semantics. To illustrate this, let’s go back to the portfolio meeting:
The manager doesn’t want to inspect the budget variance for the work item “BLK-182”; the manager just needs to know if the project (Space) “Akashi Kaiko Bridge” is still in budget, and how many hours have been invested, to check against what’s forecasted.
They don’t want to know the time spent in the work item “AGU-7”; execs want to know the total time spent across the whole project without changing to another tool. This changes the unit of analysis across the project portfolio.
As Atlassian explicitly says in the documentation, a Formula Field for work items can’t calculate values using other work items.
So, what to do when executives, managers, portfolio, program, and project managers need project-level calculations? This is where Projectrak for Jira comes into play.
Projectrak for Jira is a solution available in the Atlassian Marketplace, designed for project portfolio management with a handful of features that solve different headaches for large-scale chunks of project data. Allowing organizations to centralize and standardize projects, bringing governance closer to operational work already happening in Jira.
With Projectrak, it’s possible to ask questions such as:
asset, measuring its performance
Projectrak for Jira solves the pain of checking between 150 individual work items and, instead, having one consolidated project KPI that can actually be used in a portfolio conversation.
Instead of somebody going across different work items, exporting data with Exporter for Jira, manipulating spreadsheets, and presenting a number during the meeting, it makes it immediately older. By using Projectrak, you are already taking advantage of the data within your operational system in a structured way associated with the project (Space).
This is the important part. Jira Formula Fields for work items and Projectrak Formula Fields for projects don’t compete for the same use case. They can perfectly operate at different levels of the same information architecture:
Not every calculation in Jira belongs at the same level. Jira Formula Fields for work items are ideal for more operational calculations, such as the budget variance for a very specific task, while Projectrak Formula Fields for projects work better for managers and execs, were you can aggregate data across projects to calculate KPIs such as remaining budget, total time spent, or unresolved work.
Download the one-pager with short use cases of Formula Fields for projects or work items >>
As we have mentioned, Jira formula calculations are restricted to the data within one work item. By contrast, Projectrak can aggregate selected Jira work item data by project or space and combine those results with Projectrak custom project level fields.
Atlassian’s Jira Formula Fields for work items are an important improvement for Jira, given these calculations previously required Automation rules, additional maintenance, or spreadsheet exports, and now they can live directly on work items. However, making them smarter doesn’t create the project level context the management needs. A project portfolio isn’t actually a long collection of work items. In any case, it’s a collection of projects or spaces, each with its own budget, progress, time consumption, and operational signals.
Projectrak Formula Fields for projects help connect those two levels by taking selected data generated based on Jira work and turning it into structured project data.
Native Jira Formula Fields improve the intelligence of each individual work item.
Projectrak Formula Fields take the next step by aggregating Jira activity into project calculations to support project and portfolio decisions.
Both layers are used for the problem they were designed to solve. Teams don’t need to choose between operational detail and management context. They can have both with this new release from Atlassian.
Below, download a comparison table of Formula Fields use cases you'll be able to discover how to turn day-to-day activity into structured and reliable project information for better PMO decision-making.
This practical comparison table breaks down how Jira Formula Fields for work items and Projectrak Formula Fields for projects work together across different levels: from operational execution to management higher view reporting: