Forums

Articles
Create
cancel
Showing results forΒ 
Search instead forΒ 
Did you mean:Β 

πŸš€ Now Live: Native Formula Fields in Jira!

Esha Gajula
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 15, 2026

Hi everyone,

I’m excited to announce that Formula Fields are now Generally Available in Jira Cloud! Formula Fields allow you to run real-time calculations directly on Jira work items. By automating these calculations within Jira, you can ensure data remains accurate and actionable without needing to export to external spreadsheets.

Key Capabilities

  • Real-Time Calculations: Results update automatically whenever a referenced source field is modified.

  • Searchable & Filterable: Formula results are fully supported in JQL, allowing you to use them in dashboards, automations, and saved filters.

  • Multiple Output Types: Support for Number, Text, Date, and Duration outputs to cover use cases like risk scoring, status labeling, and due date management.

  • AI-Powered Building: Use Rovo to generate formulas from natural language prompts or suggest corrections for syntax errors.

Admin Details

  • Availability: Enabled by default across all Jira Cloud editions (Free, Standard, Premium, Enterprise).

  • Configuration: Admins can create "Formula" fields in company-managed spaces or team-managed spaces.

  • Stability: To ensure JQL and reporting stability, the output type (e.g., Number vs. Text) is locked at the time the field is created.

What’s Next?

As we move into GA, here are a few areas that are not yet supported in this release:

  • Cross Work Item Rollups: Formulas currently run within a single work item β€” calculations that span across work items (e.g., rolling up values from child work items to a parent Epic) are not yet supported. We'd love to hear from you: How would you use cross-issue rollups in your workflows? Share your use cases in the comments!

  • Select Fields: Referencing single and multi-select fields within formula logic is not yet supported. We're curious β€” how are you looking to use select fields in your formulas? Let us know in the comments!

Helpful Links:

We’re excited to see how your teams use these new capabilities. Please share your feedback and use cases in the comments!

5 answers

2 votes
Stephen Patterson
Contributor
July 15, 2026

A Select Fields use case: We currently have an automation that generates a "RICE score" where RICE represents a work item's Reach, Impact, Confidence, and Effort. Each of these is represented by a numerical value, chosen from a select list, and then, when all fields are populated, the conditions are met to then calculate a score, which is written to a "RICE score" field. The formula we use is (R+I+C)/E. It would be great to be able to use a formula field rather than depending on an automation for the calculation.

Andrea Robbins
Community Champion
July 16, 2026

Hi @Stephen Patterson this is a common practice when using Jira Product Discovery and is a formula field you can use in JPD.

0 votes
Fabio Racobaldo _Catworkx_
Community Champion
July 17, 2026

This is a great feature! Thanks for sharing 

0 votes
Italo Lobato
Contributor
July 16, 2026

This is great feature!

 

Some fields we have with Automation that I see we could replace with Formulas in the future:

Sum Story Points Below Epic

Reopen count

Comment count

 

It would be great to have a public catalog with examples on Formulas (similar  Automation for Jira has https://www.atlassian.com/software/jira/automation-template-library )

 

Matt Doar _Adaptavist_
Community Champion
July 16, 2026

The idea of more examples is a good one!

0 votes
Yatish Madhav
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
July 16, 2026

Thanks @Esha Gajula - this is quite awesome and I am looking forward to both items in the "Whats next" section.

We use work items for some automated processes like vulnerability management and count them in tickets and across multiple other tickets and would like to create calculations based on them in ticket and across tickets. We currently did some in house development and created our own dashboards for this.

As for selects, i cant think up scenarios right now, but i do see value in using them for existing fields esp as we moving more fields towards selects ... would be interesting and curious to know if and how cascading lists can be added to this mix too :)

Question for now, is this available to Jira, Service Management and Product Discovery spaces? In our instance it states it is only for JPD unless it is still rolling out to us. 

Thanks
Yatish

0 votes
zoltanersek _outpostlabs_dev_
Atlassian Partner
July 16, 2026

This is a really nice addition. I can already see a few automation rules disappearing from our instances.

One thing I'd love to see over time is support for date/time calculations using now(). There are quite a few use cases like issue age, days until due date, or "days since last updated" that currently require automation simply because the value needs to keep changing as time passes.

Even without cross-work item rollups, being able to calculate those kinds of dynamic values natively would simplify a lot of reporting and dashboards while reducing automation noise.

Suggest an answer

Log in or Sign up to answer