Release notes - November 2026 update

The November 2026 update of Stopwatch Field for Jira Cloud (Forge).

A site administrator must approve the update. This version asks for new permissions. Until a site administrator approves them, the site stays on the previous version and gets no further updates. See Permissions and approval.

Permissions and approval

This version of Stopwatch asks for one new permission:

Permission Why
manage:jira-project Show the Stopwatch issue panel per project: the app keeps in a project property which of its panels show in the project

Time in Status, Timer and Stopwatch each keep their own property, so the panels of one app never turn on or off the panels of another app installed on the same site. See Panel visibility.

How to approve

  1. In Jira, go to Settings > Apps > Manage apps.
  2. Find Stopwatch and click Update - or accept the update request in Atlassian Administration.

Until the new permissions are approved, the site stays on the previous version and gets no further updates.


New

Setting forms on tabs with a preview

The Stopwatch field setting form is split into the tabs General, Events, Calendar and Display; the Stopwatch panel form has tabs too. A tab with errors is marked, and Save opens the first such tab. The One column / Two columns button switches the layout.

Next to the form, enter an issue key to preview the value the unsaved setting gives on that issue: the field bound to the setting and its value, how the value was counted, and whether the value would be written there at all (JQL filter, issue date limit, excluded project, field context). The panel forms preview the panel the same way, and say when the panel will not be visible on that issue and why. The preview writes nothing.

See Stopwatch field settings.

“Configuration changed” after a setting is saved

When you save a change of a field setting, calendar or custom event that changes the values, the app shows Configuration changed with the number of issues and contexts that keep values calculated with the previous configuration. Recalculate now starts a full recalculation of them, Later leaves it for the Recalculation tab. The window names the changed fields and says whether the change affects the time itself or only how it is written. See After you change a setting.

Recalculate an issue from the issue view

A new Recalculate Stopwatch fields action in the issue … menu shows the values of every app field on the issue with the time each was last calculated, and queues a recalculation of just this issue. It needs the Edit issues permission, not Jira admin rights. Field values also carry a new DateLastCalculated date you can search and sort by in JQL. See Recalculate a single issue.

Health Check: Check an issue

Enter an issue key on the Health Check tab to see whether each panel of the app is shown on the issue and whether each active field setting writes its value there - and if not, why. Panel visibility can be re-synced from the same place. The check changes nothing. See Check an issue.

Show short times as “<1m” on the panels

A new option of the panel configurations, Show time under the format step as “<1”, shows a non-zero time shorter than the smallest unit of the format as <1m (<1h, <1d) instead of 0m. It is off by default and changes only the panel: field values, JQL keep the real value. See Time formats.

Stopwatch interval breakdown

The Stopwatch issue panel gets an Intervals block: counted intervals, pauses and the calendar applied. It is turned on per panel with the new Show intervals option of the Stopwatch panel configuration; it is off by default, also for existing panels. See Stopwatch panel intervals.

Custom Events in every app

The Custom Events tab is in every app of the family: Time in Status, Timer, Stopwatch and Time Between Dates. A custom event is a change of any issue field that you name once and then use as a start, pause, stop or restart event of Stopwatch and Timer fields and panels. See Custom Events.

Backups: Restore and Show diff

The Backups tab keeps snapshots of all settings, including the bindings of settings to field contexts.

  • Restore in the … menu of a snapshot applies it on this site. The current configuration is stored as a manual snapshot first, so a restore can be undone; settings created after the snapshot are kept - Restore deletes nothing.
  • Compare two backups: choose two snapshots and click Show diff to see what was added, removed or changed between them.

See Backups.


Improved

  • Field settings without a field context are marked in the row of the setting: a short Not bound label and Open Health Check.
  • License. With an inactive license (expired or cancelled) the app stops calculating and writing field values, and the admin page shows “License required”. When Jira cannot tell the state of the license, the app keeps working.

Fixed

  • ”+ Icon” display modes showed no icon. The field value again gets ▶️ while it is counting time; JQL and sorting are unchanged. No manual recalculation is needed: an issue’s value gets the icon on its next recalculation.

Moving from the Connect app

The settings that the Connect app saved for the move are imported once, automatically, when the admin page of the Forge app is opened for the first time; a setting that already exists with the same name is never overwritten. Health Check > Settings from Connect shows what was imported, lists what was not carried over and has Import again.

  • Work calendars move with the settings: each keeps its name, time zone and working schedule.
  • Custom events of the Connect app move too: they appear on the Custom Events tab, and the events of the moved settings and panels use them.
  • Upload file from Connect: if the settings did not move automatically, click Download for Forge in the Connect app and upload the file in Health Check > Settings from Connect.
  • Check the move from Connect lists the imported settings that have no field yet, with the steps to create each field, and gives a JiBrok Studio scenario that creates all of them.

See Moving from the Connect app.