Recalculation


Automatic updates

The app recalculates fields when Jira reports a change on the issue. Which fields are recalculated depends on what changed:

What happened Fields recalculated
An issue is created or updated Number of comments, the issue history fields, the link and sub-task counters, the sorting fields, the project fields and SLA breach time.
A comment is added, edited or deleted All 12 comment fields. A comment edit reaches the app as an issue update with no changed fields, and it recalculates the comment fields.
An issue link is created or deleted The link and sub-task counters, on both linked issues.

Changes that the app itself writes into its own fields do not start another recalculation.

The comment fields that compare people are also recalculated when the person they compare against changes: changing the assignee recalculates Is author of last comment assignee and Is author of first comment assignee, changing the reporter recalculates Is author of last comment reporter and Is author of first comment reporter.

The ToDo List field is not recalculated: its value is what users save.


Filling in existing issues

A new calculated field has no value on issues that existed before it was created. Values appear on an issue the next time it changes, or when you run a recalculation from the admin page.


Recalculation from the admin page

Open the app’s admin page (Jira settings → Apps → Calculated Custom Fields). You need Jira administrator permission.

Where Button What it recalculates
Overview tab Recalculate all Every calculated field on every issue.
Overview tab → click a field name → Field details Recalculate this field One field type on every issue. Not shown for the ToDo List field.
Service Info tab → Scoped recalculation Recalculate by JQL Every calculated field on the issues that match your JQL.

Before anything starts, a dialog shows “This will affect approximately N issues.” (“approximately 1 issue.” for one) Confirm with Recalculate, or Cancel.

  • Recalculate by JQL: enter a query (for example project = ABC AND created > -1w). An empty query is refused with “Enter a JQL query before triggering a scoped recalculation.” An ORDER BY in your query is ignored.
  • After you confirm, the admin page shows “Recalculation queued.” The work runs in the background in batches; you can close the page.
  • If the task could not be queued, the page shows “Recalculation was not queued: <reason>“. The reason is the background queue’s answer. The Service Info tab then shows Recalculation could not be started (see below).

Following progress: Service Info

The Service Info tab shows the state of background recalculation. It refreshes itself every 30 seconds (“Auto-refresh: 30s”); Refresh updates it at once.

Section Shows
Pending recalculations Recalculation tasks that are queued or running, as a table: Field type (the field’s name as on Overview, or All fields / By JQL), Issues, Scheduled. “No pending tasks.” when there are none.
Recalculation could not be started Shown only when the background queue refused the latest recalculation: “The background queue did not accept the last recalculation, so it did not run.” and what to do: “Run the recalculation again. If it fails again, contact support and include the task ID below.”, with the task ID and the time. The queue’s own answer is folded under Details for support; open it to copy it for support. A refused task is not retried by itself. Once a recalculation started after the refusal is queued, the section goes away.
Last batch The latest processed batch, one line per value: Finished, Duration (for example 10 s, 1 min 5 s; Less than 1 s for a short one), and Field values updated / Field values failed — field values written and failed by that recalculation task (one issue counts once per field). “No batches run yet.” before the first one.
Errors by field type How many errors each field type had, as a table: Field type (the field’s name, as on Overview), Errors, Last error. Errors of a recalculation that failed as a whole (the queue refused it, or it never started) are listed as “Recalculation that did not start (run it again)”; run that recalculation again. Queue refusals are no longer counted once a later recalculation was queued. “No errors recorded.” when there are none.
Last recalculation When each kind of bulk recalculation last finished, as a table: Field type, Completed. A field’s row is Recalculate this field (the field’s name); All fields is Recalculate all; By JQL is Recalculate by JQL.
Scoped recalculation The JQL box and the Recalculate by JQL button.

Times on this tab (Scheduled, Finished, Last error, Completed, the time of a recalculation that could not be started) are shown as a date and time in your browser’s language and time zone, for example Nov 6, 2026, 12:00:00 PM.

Finished tasks are removed from the list after 7 days. A task that never started within 2 hours is closed as failed, so it does not stay in Pending recalculations for good; start it again.


When the license is not active

Recalculation stops while the license is not active; values already calculated stay. See License.