- Accessing the admin panel
- Tabs
- Lists of settings
- Forms and dialogs
- The app is getting ready
- App information
Accessing the admin panel
The admin panel is available to Jira administrators only.
To open it:
- Go to Jira Settings (gear icon) > Apps > Manage apps
- Find Time Between Dates in the list of installed apps
- Click Configure
The admin panel opens in a new page inside Jira.
Tabs
The admin panel has 6 tabs, each responsible for a specific area of configuration: Time Between Dates, Custom Events, Calendars, Recalculation, Backups and Health Check. Import / Export and Activity Panels are only in the Time in Status app.
In a narrow window the tabs wrap onto a second row instead of shortening their names.
Time Between Dates
Configure Time Between Dates custom fields. These fields calculate the elapsed time between any two date or datetime fields on an issue, using a work calendar.
- Field Settings - define start/end date fields and display options
Time Between Dates reference →
Custom Events
Define Custom Events - named rules that fire when a specific field value changes. Time Between Dates fields do not use events, but the tab is there, as in the other apps of the family.
Calendars
Create and manage work calendars with business hours, break times, holidays, time zones, and repeating patterns. Calendars are used by all field types to calculate working time.
A built-in 24x7 calendar is always available as the default.
Recalculation
Monitor and manage data freshness across all fields and contexts.
- View freshness statistics (up-to-date, stale, unprocessed issues)
- Start batch recalculation jobs (full, unprocessed only, or stale only)
- Monitor batch job progress and errors
- Pause and resume all background processing
- Detect and clean up orphaned field contexts
Backups
The Backups tab keeps snapshots of all settings, including which settings are bound to which fields and contexts.
- A snapshot is taken every hour, but stored only when the configuration has changed.
- Backup now stores a snapshot at once.
- The 30 latest snapshots are kept; older ones are deleted.
The list shows the date (in your browser’s time, for example “2026-11-07 10:34”), the type (scheduled or manual), the contents (for example “4 settings, 1 binding, 2 calendars”) and the size. The … menu of a snapshot has:
| Action | What it does |
|---|---|
| View | The contents by section, with names: settings, panels, calendars, custom events and field context bindings (field, context, field type and setting), and the raw JSON |
| Download (import) | A file in the format of Import / Export, to move the settings to another site |
| Download (full) | The full snapshot |
| Restore | Applies the snapshot on this site - see Restoring a backup |
Compare two backups shows what was added, removed or changed between two snapshots: choose the older and the newer snapshot in the two lists and click Show diff.
To move settings to another site, use Download (import) and import the file on the Import / Export tab of the Time in Status app.
Backups may contain account IDs of users chosen in conditions; when a user account is closed, the app removes it from backups too.
Restoring a backup
Restore in the … menu of a snapshot applies it on this site. After you confirm:
- The current configuration is stored as a manual snapshot first, so a restore can be undone by restoring that snapshot.
- Settings, calendars and bindings of settings to field contexts are taken from the snapshot. A setting with the same name returns to its state in the snapshot; a missing one is created again.
- Settings created after the snapshot are kept - Restore does not delete anything.
A message shows how many items and bindings were restored, and the errors, if any (for example, a setting that refers to a calendar that is no longer there). Restore does not recalculate issues: to apply restored settings to values already on issues, run a recalculation.
Health Check
The Health Check tab finds what keeps the app from calculating or showing values, and tells what to do. The tab label shows the number of broken items in red. Refresh now checks again. Next to it the tab shows when the last check ran: “Last checked just now” during the first minute, then “Last checked 2m ago”, “Last checked 1h ago”, updating by itself while the tab is open. With nothing found: “All clear - No broken references found. Every setting points to statuses, fields and contexts that still exist in Jira.”
On the Time Between Dates tab, a setting that is not bound to a field context shows a short Not bound label under its name, then Not bound to a field context - nothing is calculated and an Open Health Check button that leads here.
Check an issue
At the top of the tab, enter an issue key (for example PROJ-123) and click Check. For this issue you see whether each active field setting writes its value - and if not, why. The check changes nothing - no field values, no settings.
Each row has a label: green OK - shown or written; grey (Not configured, Hidden at zero, Not in scope) - not shown or not written because the settings say so; orange Problem - the state contradicts the settings or could not be checked.
Field settings - one row per active field setting of the field types your app includes, with the first reason that stops the value:
| Result | What to do |
|---|---|
| Problem - Not written: the field setting is not bound to any field context | Open the custom field context in Jira and select this field setting - see Field context configuration. |
| Not in scope - Not written: the issue does not match the JQL filter of the field setting | Change the JQL filter if this issue should get a value. |
| Problem - Unknown: Jira did not answer the JQL filter check | Check again in a few minutes; if it keeps failing, check the JQL filter. |
| Problem - Not written: the app is excluded from the project of this issue | See Projects this app is excluded from. |
| Not in scope - Not written: the issue is older than the date limit of the field setting | Move the date limit back if older issues should get a value. |
| Not in scope - Not written: the issue is outside every field context bound to the setting | Add the project and issue type to the custom field context in Jira. |
| OK - Value is written | - |
If no issue has that key, or the app cannot see it, the check says that the issue is not found.
Sections
| Section | Meaning |
|---|---|
| Field contexts without a field setting | Contexts of the app fields where nothing is calculated. Configure opens the context. |
| Field settings without a field context | Active settings that write no values, with where the setting came from (migration, import, Connect upgrade, or “Created in this app, never bound”). The binding manifest hint is shown only when a setting really came with a transfer. In the Action column, choose a field and its free context and press Bind: with exactly one free context it is already chosen, with several you pick one. Open setting opens the setting. |
| Fields whose name is not unique in Jira | Several fields with the same name can make JQL by field name ambiguous. |
| Contexts whose issue counts are not updating | The query that counts the issues of a context is invalid or Jira keeps failing it; shows what Jira says. |
| References to deleted working calendars | Time is counted around the clock until a calendar is chosen again. |
| Projects this app is excluded from | See below. |
| Field contexts whose issues are not being counted | Contexts the app could not read, with the reason and since when; re-checked every hour. |
| Settings pointing to deleted statuses | Remove reference removes the deleted status from the setting. |
| Settings pointing to deleted fields | Remove reference removes the deleted field. |
| Orphaned field-context mappings | Bindings whose setting, project, issue type, context or field was deleted. |
Remove reference asks first; the setting keeps working. The window warns when removing a reference removes more: a setting whose date field was deleted.
Health Check also shows when background work is paused (no app fields, or the license is not active).
Projects this app is excluded from
This section lists the projects where Jira rejects the app’s writes: every attempt to save a field value there is answered with This app is excluded from the following projects. The app skips issues of these projects entirely - they are neither recalculated nor searched, so their fields have no values.
This is a restriction set on the Jira or Atlassian organization side, not an error in the app or in your settings. To find the cause:
- Ask your Jira or organization admin whether the app’s access to these projects was restricted around the First seen date shown in the table - for example, by a data security policy in Atlassian Administration (admin.atlassian.com → Security → Data protection → Data security policy).
- Once the restriction is lifted, the project leaves the list by itself within a day and its values appear again.
- If you cannot find the cause, contact support with the project key and the dates from the table.
Settings from Connect
At the bottom of the tab, Settings from Connect shows the settings that the Connect edition of Time Between Dates saved for the move to Forge: whether they were found, when they were imported and with what result - for example Imported on …: N created, N already existed, N failed - and a list of what was not carried over. Import again repeats the import, and Upload file from Connect takes the settings from a file downloaded in the Connect app. Settings that already exist with the same name are never overwritten.
Next to it, Connect to Forge migration audit lists the old Connect fields, the saved filters and the dashboard gadgets that still refer to them. See Moving from the Connect app.
Lists of settings
- Time format shows an example of the format, for example
13h 48m 03s. - A long setting name wraps inside the Name column instead of taking the width of the other columns; the column headers stay on one line.
- A setting that is not bound to a field context shows a short Not bound label under its name, then “Not bound to a field context - nothing is calculated” and Open Health Check.
Forms and dialogs
- Names of settings, panels, calendars and custom events: required, unique, up to 150 characters, without
\ / > < & %. - JQL filters: up to 4000 characters, without
ORDER BY; Jira checks the JQL on save. - Forms and confirmations open as Jira dialogs: the whole Jira page, including its header and menu, is dimmed while a dialog is open. The dialog size follows the form; a long form scrolls inside the dialog as a whole, and the preview of a setting or a panel scrolls together with the form.
- A click outside the window closes a form, like any Jira dialog. Escape closes it too, but only when the focus is not inside the form: while you type in a field, Escape does nothing - use Close or click outside the window. Escape in an open drop-down list closes only the list.
- If the form has unsaved changes, it closes and opens again within about a second, after Jira has finished closing the previous window, with your changes and the question Discard unsaved changes?: Keep editing returns to the form, Discard closes it without saving. Your changes are kept the same way whether the window was closed by Escape or by a click outside it. Close asks the same question only when the form really differs from what it was opened with; changing a value and setting it back closes the form without the question.
- Save with a mistake in the form does not save and says so: the message “Can’t save: fix the highlighted fields” names the first field with its error (for example “Name: Not valid symbol in name”), and the form scrolls to that field, switching to its tab when needed. If Jira refuses to save, the message “Save failed” shows the reason.
- If a setting refers to statuses, fields or calendars deleted in Jira, the form says so: “No longer exists in Jira (will be removed on save)” or asks to select another value.
- Delete and Restore confirmations close first, then the item is deleted or restored and a message reports the result.
- Deleting a field setting keeps the values already stored on issues until the field is recalculated or cleared. Deleting a panel configuration stops showing the panel; data is not affected.
- After you save a change that changes the values, the Configuration changed window offers to recalculate.
The app is getting ready
Right after installation or an update the page may show The app is getting ready - “The app is finishing its setup after installation or update. This usually takes about a minute.” Click Refresh in a minute.
With an inactive license the page shows only that a license is required - see Troubleshooting.
App information
At the bottom of the admin panel, you can find the app information badge showing:
- App version - the currently installed version
- Environment - development or production
- Installation ID - unique identifier for support requests

