- Permissions and approval
- New
- Count only while: conditions on issue fields
- Download CSV in the Activity panel
- Start counting from the next business day
- Setting forms on tabs with a preview
- “Configuration changed” after a setting is saved
- Recalculate an issue from the issue view
- Health Check: Check an issue
- Show short times as “<1m” on the panels
- Timer interval breakdown
- Stopwatch interval breakdown
- Custom Events in every app
- Backups: Restore and Show diff
- Improved
- Fixed
- Data Center migration
The November 2026 update of Time in Status for Jira Cloud (Forge).
Permissions and approval
This version of Time in Status asks for two new read-only permissions:
| Permission | Why |
|---|---|
Read user information (read:jira-user) |
Show assignee names in the CSV file downloaded from the Activity panel, pick people in Count only while conditions, and read the site’s time zone for the day boundaries of 24x7 counting without a calendar time zone |
Read field options (read:field.option:jira) |
Pick values of select lists and similar fields in Count only while conditions |
The app does not change users or field options and sends nothing outside Atlassian: egress is unchanged, the app keeps running on Atlassian infrastructure. Every permission of the app is listed in the Permissions Reference.
How to approve
- In Jira, go to Settings > Apps > Manage apps.
- Find Time in Status 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
Count only while: conditions on issue fields
A Time in Status field setting can count time only while the issue is in the selected statuses and its fields meet conditions - for example, only while Priority is High. The value of each field at every moment is restored from the issue history. Operators depend on the field type (is one of, contains any of, is empty, greater than, between, is before, …); conditions are combined with all / any and grouped, up to 20 conditions on up to 9 fields. The value is recalculated when a condition field changes on the issue. Export and import carry the conditions, and Health Check explains an issue whose value is 0 because the conditions were never met. See Count only while.
Download CSV in the Activity panel
The Activity panel has a Download CSV button: the report of the open tab downloads at once, without a dialog, and includes assignee names. Each user can choose the separator (comma, semicolon or tab) next to the button; the default separator is set by the admin in the panel configuration. See Download CSV.
Start counting from the next business day
A new option of the Time in Status field setting: time before the start of the first working day after the issue was created is not counted. Day boundaries and working hours come from the setting’s calendar; with Default 24x7 counting starts at the next midnight. See Start counting from the next business day.
Setting forms on tabs with a preview
The field setting forms are split into tabs - Time in Status: General, What to count, Calendar, Display; Timer: General, Events, Goals, Calendar, Display; Stopwatch: General, Events, Calendar, Display; Time Between Dates: General, Dates, Calendar, Display. The panel forms (Time in Status, Stopwatch, Timer) have 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 Time in Status field settings, Timer, Stopwatch and Time Between Dates.
“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 Time in Status 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 and the CSV file keep the real value. See Time formats.
Timer interval breakdown
The Timer issue panel can expand the value into its intervals: each counted run and pause with its start, end and counted time, the calendar applied and the goal source. It is turned on per panel with the new Show intervals option of the Timer panel configuration; it is off by default, also for existing panels. See Timer panel intervals.
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
- Sorting by duration in the issue navigator. The field setting forms explain that the field column sorts by the displayed text and give the exact
ORDER BY "<Field name>.<alias>"JQL to sort issues by the duration itself. - Field settings without a field context are marked in the row of the setting instead of a large banner over the whole tab; Health Check and the Recalculation tab still list them.
- Health Check: projects the app is excluded from points to the real place of the rule - Atlassian Administration, Data security policy.
- Timer goal. The goal is re-evaluated on every recalculation.
- Recalculation progress is honest and faster, including the recalculation that runs after a migration.
- Large projects and histories. Sites with many projects see all of them; issue history and comments are read to the end, so the Activity panel no longer stops short on long histories.
- Recalculation jobs survive interruptions: a page of a job keeps the issue history it already fetched, and a retried page no longer repeats issues it already wrote.
- No duplicate background work. The hourly check no longer duplicates a recalculation job that is already running for the same context.
- License. When the app license is reliably inactive (expired or cancelled), events, queues and schedules stop calculating and writing fields, and the admin page and field settings show that a license is required. When the license state is unknown, 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.
- Transition time of an incrementally updated value could be shifted by the event delivery delay; it is now read from the event.
- Recalculation job stuck in Pending for 7-9 minutes when its next page met a busy queue; the page is now rescheduled.
- Health Check “not being counted” rows stayed up to 3 hours with an outdated reason after the cause was fixed; Health Check now re-checks them.
- “License required” notice was not shown on the field settings card and on the date and time fields list when they were refused for licensing.
- Field setting form hint promised to create a Jira field on save, which never happens; it now says to bind the setting to a context of an app field.
- Recalculation jobs
- A temporary Jira 400 on a job page is retried instead of failing the job; an invalid JQL fails with its own reason and the parser message.
- Failed jobs are retried by the age of the failure, not of the job start, and final failures are not retried.
- The automatic backfill no longer cancels a live job that waits in a busy queue.
- A field recalculation no longer finishes with part of the issues of the context silently not processed; a job that still skips issues reports how many and why.
- An event released after repeated lock contention is kept for a later pass instead of being dropped.
- Background errors in the queue consumer, the five-minute schedule, the migration handler and the admin page backend.
Data Center migration
Moving Time in Status, Stopwatch, Timer and Time between dates settings from Data Center to Cloud with the Jira Cloud Migration Assistant (JCMA):
- No silent Data Center ids. A project, issue type, status or field without a Cloud match is left out with a warning; manual import without migration maps does not guess.
- Migration warnings with their text are written to the JCMA migration log, not only their count.
- Field maps. Field ids are matched in both forms (
customfield_NandN), so field bindings find their field after migration. - Calculation meaning is preserved: status mode follows the Data Center rule, and the calendar flags and custom events are migrated or warned about.
- JQL in settings is remapped - in field settings, Timer goals and Stopwatch overrides, including
project = N,issuetype = Nandstatus was / changed. - Timer goal date field is remapped by the field map instead of only being warned about.
- Field context bindings: a binding made by an admin before the migration is kept, a context collision does not overwrite, and a setting is matched by name within its own type.
- Panels, roles and calendars: Timer and Stopwatch panels follow “show as panel”, and roles and calendars with the same name are handled.
- Repeat migration updates what the previous JCMA import created and leaves settings edited by an admin as they are.
- Recalculation after migration starts by itself for the migrated projects, after Jira Cloud has indexed their issues, and Health Check shows its progress. While processing is paused it waits; time spent paused does not count towards its 12-hour limit.
- Manual import with a binding manifest finds the setting by name within its own type, ignoring case, as the JCMA path does.

