- Field shows no value / recalculation says “No field contexts configured”
- Admin shows “The app is getting ready”
- Admin shows “This app requires an active license”
- Panel is not visible on the issue
- Field values are not updating
- Timer is not starting
- Calendar changes not reflected in values
- JQL search returns no results
- Timer shows “Failed” but issue was resolved on time
- Web panel shows different values than the custom field
- Contact support
Field shows no value / recalculation says “No field contexts configured”
Start with a check: Check an issue on the Health Check tab takes the issue key and names the first reason the field gets no value on it - from the list below.
Possible causes and fixes:
-
Field setting is inactive - open the admin panel, find the field setting, and make sure the Active toggle is on.
-
No field context binding - the Jira custom field must be bound to a field setting via its context. Go to Jira Settings > Issues > Custom fields, find the field, open Contexts and default value, then in the context’s block open Custom field config > Edit custom field config and verify a field setting is selected. See Field context configuration.
You can spot an unbound setting in the admin panel: on the Timer tab its row is marked Not bound to a field context - nothing is calculated, with an Open Health Check button. The Health Check tab lists all unbound settings, and the Recalculation tab lists unbound contexts.
-
JQL filter excludes the issue - if the field setting has a JQL filter, the issue may not match it. Check the JQL filter in the field setting and verify the issue matches.
-
Issue date limit - if the field setting has an Issue Date Limit, issues created before that date are not processed.
-
Recalculation needed - for existing issues, the app needs to process their changelog. Go to the Recalculation tab and run a recalculation for the affected context. For a single issue, choose Recalculate in the issue’s ••• menu - see Recalculate a single issue.
-
Processing is paused - check the Recalculation tab for “All processing is paused”. If paused, click Resume all processing.
-
The project is excluded from the app - if Jira rejects the app’s writes in a project, the app skips its issues entirely and they have no values. Check the Projects this app is excluded from section on the Health Check tab.
-
The app license is inactive - see Admin shows “This app requires an active license”.
Admin shows “The app is getting ready”
Right after installation or an update the admin page may show The app is getting ready - The app is finishing its setup after installation or update. This usually takes about a minute. Nothing is wrong: click Refresh in a minute.
Admin shows “This app requires an active license”
The admin panel and the field context configuration page show This app requires an active license. Check the app license in Manage apps. instead of their content. Jira reports the app license as inactive.
What stops: the app does not recalculate or write field values - not on issue events, not in background sweeps, not in batch recalculation.
What keeps working: values already calculated stay on issues. The issue panel, JQL searches by values and the Calendar Select field keep working.
If Jira does not pass the license status at all, the app works normally - the notice appears only when the license is definitely inactive.
Fix:
- Check the app license under Jira Settings → Apps → Manage apps and renew it if needed.
- Run a Full recalculation on the Recalculation tab. After renewal the app does not catch up on the missed changes by itself.
Panel is not visible on the issue
Start with a check: Check an issue on the Health Check tab shows, for the issue’s project and issue type, which panels the visibility settings show.
Possible causes and fixes:
-
Panel visibility not configured - panels are hidden by default. You need to enable them via panel visibility settings. Check that the
tis-cloud-panels-timerproject property (or the app-leveltis-cloud-panelsproperty) includes thetmrpanel type for the relevant issue type. -
No web panel configured - creating a web panel in the admin panel defines what to show, but you also need panel visibility to control where it appears. Make sure both are set up.
-
Wrong project or issue type - if the web panel is scoped to specific projects or issue types, the issue may not match.
-
Jira caching - Jira may cache panel visibility. Try refreshing the issue page or waiting a few minutes.
Field values are not updating
Possible causes and fixes:
-
Processing is paused - check the Recalculation tab for “All processing is paused”, and click Resume all processing. Counting of one context can also pause by itself when Jira does not complete its issue-count request several times in a row - the tab shows until when; Refresh on the context counts it now.
-
Rate limits reached - if your instance generates a high volume of updates, the app may be throttled. Values will continue updating at a reduced rate. See Technical limits.
-
Field is inactive - verify the Active toggle in the field setting.
-
Scheduled refresh timing - some updates happen on a schedule (every 5 minutes or hourly) rather than immediately. For running timers, the
DateNextUpdateproperty controls when the next refresh occurs. -
Check freshness - go to the Recalculation tab and click Refresh on the relevant context to see current freshness statistics.
-
One issue only - open the issue and use the Recalculate action in its ••• menu: it shows when each app field was last calculated and recalculates them on demand.
Timer is not starting
Possible causes and fixes:
-
No matching event trigger - verify that the start events in the field setting match the actual changes happening on the issue. For example, if the start event is STATUS_TO “In Progress”, the issue must transition to “In Progress” (not just be in that status already).
-
Event not in changelog - the app reads the issue changelog to detect events. If a change does not appear in the changelog (e.g., bulk operations that skip changelog), the trigger will not fire.
-
Wrong event type - make sure you are using the correct trigger type. For example,
STATUS_TOrequires an exact status ID match. Check that the status IDs in your trigger match your workflow. -
Custom event misconfiguration - if using CUSTOM_EVENT triggers, verify the custom event’s field, action, and value settings match the actual changes. Health Check lists events that refer to a deleted custom event.
-
Already in target state - a start event only fires if the timer is in a state that allows starting: Inactive, Paused (where it resumes) or a stopped state - Completed or Failed - where it opens a new cycle. If it is already Running, start events are ignored. A start from a stopped state is also ignored when Calculate type is
ONLY_FIRST_START, because only the first cycle counts. -
Run recalculation - after fixing triggers, run a Full recalculation to reprocess existing issues from their changelog history.
Calendar changes not reflected in values
After modifying a calendar (changing working hours, adding holidays, changing timezone), existing field values are not automatically recalculated.
Fix: Go to the Recalculation tab and run a Full recalculation for all contexts that use the modified calendar.
JQL search returns no results
Possible causes and fixes:
- Wrong syntax - Forge uses schema properties, not the Connect entity property syntax. The correct syntax is:
"Your Field Name.PropertyAlias" operator valueSee Timer JQL for the correct syntax.
-
JQL by a property finds nothing - check that the property alias is written inside the quotes of the field name, after a dot:
"Your Field Name.SecondsValue" > 0. Jira answers a query with a wrong property with an empty result, not with an error, so an empty list does not mean that no issues match. To see the error, paste the query into the advanced search of the issue navigator. -
Case sensitivity - text property values (StateValue, DisplayValue) are case-sensitive. Use
"Running"not"running". -
Field name mismatch - the field name in JQL must exactly match your Jira custom field name, including spaces and capitalization.
-
Field has no value - if the field has not been calculated for any issues (no recalculation run), there are no values to search. Run a recalculation first.
- Wrong property alias - verify you are using the correct property alias from the documentation. For example, use
TimeInHoursValue(nottimeInHoursValueorTimeInHours).
Timer shows “Failed” but issue was resolved on time
Possible causes:
-
Wrong calendar - the timer may be using a 24x7 calendar while you expected business hours. Check the calendar in the timer field setting.
-
Goal misconfiguration - if using JQL-based conditional goals, a different goal may have matched than expected. Check the goal order (first match wins).
-
Pause events missing - if the timer should pause during certain periods (e.g., “Waiting for Customer” status) but no pause events are configured, time accumulates continuously.
-
Calendar Select field - if a Calendar Select field is configured but the issue does not have a value, the timer uses the default calendar which may have different hours.
Web panel shows different values than the custom field
This is expected behavior. Web panels and custom fields can have different configurations:
- Different calendars
- Different time formats
- Different event triggers
Each configuration calculates independently. If you want them to show the same values, make sure both use the same calendar, events, and settings.
Contact support
If you cannot resolve your issue with the steps above:
- Go to the admin panel and note the App version and Installation ID from the app info section
- Describe the issue, including:
- What you expected to happen
- What actually happened
- The field type and setting name
- The issue key where you see the problem
- Contact support through the Atlassian Marketplace or the app’s support channels

