Slide Rule: Calculated Fields for Jira

Fields that compute themselves — and stay right on the board, in JQL and in your export, not just on the work item. Write a formula once, and every work item it applies to carries the answer. One edition, everything included, US$0.45 per user per month, free for ten users or fewer.

Jira Misc Custom Fields charges $1.00. Awesome Custom Fields charges $1.06. Abacus charges $1.44.


Getting started

1. Install

Install from the Marketplace listing, or in Jira go to Apps → Explore more apps and search for Slide Rule. You need to be a Jira administrator.

2. Create your first calculated field

  1. Go to Settings (cog) → Apps → Slide Rule.
  2. Choose New field and name it, for example Remaining budget.
  3. Write the formula using other Jira fields, for example {budget} - {spent}.
  4. Pick the result type — number, duration, date or text — and save.

3. Put it on the screen

  1. Go to Settings (cog) → Issues → Screens and add the new field to the screens you want it on, exactly as you would any custom field.
  2. Open a work item: the value is calculated and shown.

4. Use it like a real field

The result is written back to Jira, so it works in JQL, on board cards, in dashboards, in filters and in exports — not just on the screen you are looking at.

If something looks wrong

The number is in Jira, not just on the screen

This is the part most calculated-field apps on Cloud get wrong, and it is not their fault: Forge invokes a custom field's value function only on the issue view. An app built that way shows you the right number on the work item and a stale one — or nothing at all — on the board, in the backlog, in a JQL search and in a CSV export.

Slide Rule does not compute on read. It recomputes when something changes and writes the value into Jira's own index, so:

Nothing in Jira has to know this app exists for the number to be there.

A formula language that is actually a language

The loudest complaint in this category is aimed at the market leader, by its own customers:

"Has EXTREMELY limited scripting capabilities in Jira Cloud."

So the language is the product:

{Story Points} + SUM(CHILDREN({Story Points}))
IF({Time Spent} > {Original estimate}, "over", "on track")
WORKDAYS_BETWEEN(NOW(), {Due date})
SUM(LINKED({Story Points}, "is blocked by"))
ROUND(100 * COUNT(CHILDREN({Resolution})) / COUNT(CHILDREN({Summary})), 1)

Real precedence. Short-circuiting and / or, so {Divisor} != 0 and 10 / {Divisor} > 1 is safe to write. IF, COALESCE, ISBLANK, IFERROR. Rollups over children, the parent and links — narrowed to one link type when you want it. SUM, AVG, MIN, MAX, COUNT. ROUND, FLOOR, CEIL, ABS. CONCAT, UPPER, LOWER, TRIM, LEN, LEFT, RIGHT, CONTAINS, REPLACE. NOW, TODAY, DAYS_BETWEEN, WORKDAYS_BETWEEN, DATE_ADD, and date arithmetic that knows the difference between a calendar day and Jira's eight-hour working one.

Field names go in braces, exactly as Jira spells them: {Story Points}, {Due date}.

When a number is wrong, the work item tells you why

Every work item carries a Slide Rule panel showing the formula, the values it actually read on this work item, what it produced, and when. The support question in this category is always "why does it say that", and the answer is on the screen instead of in a ticket.

It refuses rather than guessing

A wrong number that looks reasonable is worse than a blank one, so Slide Rule writes nothing — and says so on the work item — when:

It also treats an unknown field name as an error, not as blank. A typo that reads as zero is how a wrong total reaches a board and nobody notices for a month.

No per-project setup

There is no per-project configuration screen, because there is nothing to configure per project. A field defined with no scope applies to every project and every work item type the moment you save it, and scoping it to certain projects is one field on the same form.

The one Jira step that remains is the one every custom field needs: add the field to a screen if you want it visible on the work item itself. Board cards, JQL, filters and exports do not need it — the value is in Jira's index either way — and the Slide Rule panel on each work item shows the value and the formula whether the field is on a screen or not.

Runs on Atlassian

The manifest declares no external permissions of any kind — no fetch, no egress, no remote backend, no analytics, no runtime AI call. The app is not technically capable of contacting any host other than Atlassian's own APIs, and every value is computed inside your own site. Two of the five apps in this category cannot say that.

What it does not do, said before you buy

Pricing

Free for up to 10 users. Then US$0.45 per user per month, falling in every band above 100. One edition; everything on this page is in it.