VersionSelectTroubleshoot VersionSelect
| Symptom | Check and next action |
|---|---|
| Field missing | Verify that the global field is on the correct project screen or work type layout and that you are viewing the intended installation. |
NOT_CONFIGURED | Save a manual catalog, or save both an API URL and catalog token. Selecting a source without saving is insufficient. |
LICENSE_REQUIRED | API integration requires an active subscription or evaluation. Use Manual configuration or activate the subscription before retrying. |
AUTHENTICATION_FAILED | Check whether the catalog credential expired or lacks access. Replace it in settings; never paste it into a support request. |
UNREACHABLE | Check public HTTPS reachability from Forge, TLS, origin approval, rejected redirects, and slow responses. |
RATE_LIMITED | Wait and retry, then review the catalog service's request limits. Cache misses and searches may create requests. |
INVALID_RESPONSE | Validate JSON, pagination metadata, names, and response size against the API contract. An HTML login or error page is invalid. |
| Selected option is missing | Confirm its group, name, and current source. Removed options and renamed API services are not recovered from existing Jira values. |
| Only 10 versions appear | Search for older versions and use Load more. The initial list intentionally shows recent versions. |
| Catalog changed or save is in progress | Let the other save finish, reload settings, review the draft, and retry. Refreshing discards unsaved changes. |
| Import rejected | Check JSON syntax, schemaVersion: 1, names, duplicate versions, and file or service size limits. |
| Saved value cannot be selected again | This is expected after removal from the current catalog. The saved Jira snapshot remains readable, but the app has no saved-history search. |
| Deleted option remains in an open editor | Close and reopen the editor after saving so it reloads the active source. |
| REST or automation exceeds Maximum entries | Only the picker enforces a configured limit below 20; Jira's hard limit is 20. |
If the catalog is unavailable, existing Jira field values remain intact, but the picker cannot use those values as a fallback catalog. Restore the catalog before searching or adding options.
What to include in a support request
Provide the app version and environment, approximate time and timezone, catalog mode, visible error code, and reproduction steps using synthetic service names. Share the Jira site identifier privately only when needed to identify the installation.
Do not send passwords, bearer tokens, raw request headers, entire work items, or unredacted exports. Log sharing is not required to submit a support request.