Recalculation and data freshness


Overview

The Recalculation tab in the admin panel lets you monitor and manage the freshness of field values across your Jira instance. It shows which issues have been processed, which are stale, and lets you trigger batch recalculation jobs.


When to recalculate

You should run a recalculation when:

  • New field setting created - existing issues need their values calculated for the first time
  • Field setting changed - when you save a change of a field setting, calendar or custom event that changes the values, the app offers the recalculation itself - see After you change a setting
  • Issues seem stale - field values have not updated as expected. For one issue, use Recalculate on the issue instead of a batch job
  • After initial setup - to backfill values for all existing issues

After you change a setting

When you save a change of a field setting, calendar or custom event that changes the values, the app opens the Configuration changed window with the number of issues and contexts that keep values calculated with the previous configuration. Jira updates such a value only when the issue changes or its update is due.

The window opens about a second after the form closes, once Jira has finished closing the form.

Button What it does
Recalculate now Starts a Full recalculation of the affected contexts
Later Closes the window; you can start the recalculation from the Recalculation tab any time

What the window tells you:

  • Whether the change affects the time itself or only how it is written (format, display mode, show type, status order, rounding).
  • Which fields changed, named as in the form - for example “Changed: Timezone”.

Some changes need no window:

  • A change of the name does not need recalculation.
  • If none of the affected settings is bound to a field context yet, there is nothing to recalculate: the app shows only the usual “… updated” message and no window. Bind the setting to a context in Jira (Health Check lists the settings that wait for one), and the new values are calculated from then on.

Data freshness

The Recalculation tab shows freshness statistics for each field and context combination.

Freshness categories

Category Description
Up-to-date Issues whose field values are current and valid.
Stale Active issues whose field values exist but may be outdated (e.g., DateNextUpdate is in the past). Only active fields can be stale — a running stopwatch. Stopped, completed, and inactive fields are considered up-to-date regardless of DateNextUpdate. The scheduled handlers process stale issues automatically, but you can trigger immediate recalculation.
Unprocessed Issues that have never had their field values calculated. These need a recalculation to get initial values.

Freshness bar

Each field context shows a stacked bar with the proportion of up-to-date (green), stale (yellow), and unprocessed (gray) issues. Click Refresh to update the freshness data.

The list shows Scope, Setting, Freshness and Last Recalculation for every field context bound to a setting; “Overall” sums the contexts up. Search by field or setting and filter by All, Needs attention, Up to date, No data and Orphaned. A disabled setting shows “Setting disabled - values are not calculated”.

Paused counting of a context

If Jira does not complete the issue-count request of a context on several runs in a row, counting of that context pauses until the time shown in the message (in your browser’s time, for example “2026-11-07 10:34”). Refresh on the context counts it now. Health Check lists such contexts under “Contexts whose issue counts are not updating”.


Running a recalculation

Recalculation modes

Mode Description
Full Recalculate all issues in this context. Use after significant configuration changes.
Unprocessed Only calculate values for issues that have never been processed. Use for initial backfill.
Stale Only recalculate issues with stale data (DateNextUpdate in the past). Use for targeted refresh.

How to start

  1. Find the field and context in the Recalculation tab
  2. Click the Recalculate button
  3. Select the mode (Full, Unprocessed, or Stale)
  4. The batch job starts in the background

Monitoring batch jobs

Active and recent batch jobs show:

Field Description
Status Pending, Running, Completed, Failed, or Cancelled
Progress Processed / Total issues with progress bar
Errors Number of issues that failed to process, with error details
Duration How long the job has been running

Cancelling a job

Click Cancel on a running job to stop it. Already-processed issues keep their updated values.


Recalculate a single issue

When only one issue looks wrong, you do not need a batch job. Open the issue, click ••• (more actions) next to the issue actions and choose Recalculate Stopwatch fields. The item is named after the app, so with several apps of the family installed you can tell the items apart: Recalculate Time in Status fields, Recalculate Timer fields, Recalculate Stopwatch fields, Recalculate Time between dates fields.

What the window shows

The window lists the values of the app fields on this issue and when they were last calculated. For each app field on the issue:

  • the field name;
  • its value, or “Not calculated yet”;
  • Last calculated - the date and time of the last calculation in your browser’s time, for example “2026-11-07 10:34”, or “Unknown” for values written before this information existed.

If no field setting of the app writes to the issue, the window says only “No field setting of the app writes to this issue.” There is nothing to recalculate then, and the window has only the Close button.

Recalculate

Click Recalculate. All app fields of the issue are recalculated, the same way as after a change of the issue. The window says “Recalculation queued, values update within a minute” and refreshes the values every 10 seconds for a minute, so you see the new Last calculated time without reopening it. When the new values arrive, the message changes to “Recalculated” with the time of the new calculation, and you can click Recalculate again.

Who can use it

  • Any user with the Edit issues permission on the issue; Jira admin rights are not needed. Without it the window shows “You need the Edit issues permission to recalculate this issue.” and the button is disabled.
  • The app needs an active license.

The time of the last calculation is also stored in the field value as DateLastCalculated, so you can find values that were not recalculated for a while: "<Field name>.DateLastCalculated" < -7d.

To find out first why an issue gets no value at all - JQL filter, issue date limit, excluded project or field context - use Check an issue on the Health Check tab.


Processing pause

You can pause all background processing globally. While pause is on:

  • Scheduled recalculation cycles are skipped
  • Event-driven updates (issue create/update) are skipped
  • Batch jobs do not run: Disable all updates cancels all active jobs. Issues a job already processed keep their new values; start a new job after you resume.

Use this during maintenance or when you need to make multiple configuration changes without triggering intermediate recalculations.

To pause: click Disable all updates on the Recalculation tab. The tab then shows “All processing is paused”. To resume: click Resume all processing.


Orphaned contexts

An orphaned context occurs when:

  • A Jira custom field is deleted, but its context data remains in the app
  • A field context is removed from Jira, but the app still has a binding for it

The Recalculation tab detects orphaned entries and lets you clean them up:

  • Cleanup orphaned field - removes all data for a deleted custom field
  • Cleanup orphaned context - removes data for a deleted field context

How automatic updates work

The app updates field values through several mechanisms:

Mechanism Trigger Frequency
Event-driven Issue created or updated Immediate (via queue)
Frequent scheduled refresh Picks up stale active fields Every 5 minutes
Slow scheduled refresh Periodic maintenance sweep Every hour

Scheduled refresh cycles pick up active issues with DateNextUpdate in the past and recalculate them. The further in the future the next update is needed, the less frequently the value is refreshed.


Tips

  • Full recalculation is safe: running a Full recalculation does not duplicate or corrupt data. It simply recalculates all values from the issue changelog.
  • Large instances: for instances with many issues, Full recalculation may take time. Monitor progress in the batch job status area.
  • Errors are per-issue: if a batch job shows errors, click to see which specific issues failed and why. Common causes: issue deleted during processing, permission issues, or rate limiting.
  • Pause before bulk changes: if you are making multiple configuration changes (updating calendars, events, settings), pause processing first, make all changes, then resume and run a Full recalculation.