Version Select Support
For help with Version Select for Jira, email support@fogsea.top.
Include the app version and environment, approximate time and timezone, catalog mode, visible error code, and reproduction steps using synthetic service names. Provide 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.
Troubleshooting
| 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 |
Backend API integration requires an active subscription or evaluation. Switch to Manual configuration or activate the app 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, the approved API origin, rejected redirects, and slow responses. |
RATE_LIMITED |
Wait and retry, then review the catalog service's request limits. |
INVALID_RESPONSE |
Validate JSON, pagination metadata, names, and response size against the API contract. An HTML login or error page is not a valid response. |
| Selected option missing | Confirm its group, name, and current source. Removed options and renamed API services are not recovered from existing Jira values. |
| Only ten versions appear | Search for older versions and use Load more. The initial list intentionally shows recent versions. |
| Import rejected | Check JSON syntax, schemaVersion: 1, names, duplicate versions, and file/service size limits. |
| Deleted option appears in an open editor | Close and reopen the editor after saving the catalog so it reloads the active source. |
If a 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.
Data deletion
- Jira field values remain in Jira until an authorized Jira user edits or deletes the issue or field data, subject to the customer's Jira retention rules.
- Customer administrators can remove active manual catalog entries and can delete the stored API token from the Version Select settings page.
- Removing an active catalog entry does not rewrite older manual-catalog revisions or existing Jira field values.
- Uninstalling the app does not imply immediate physical erasure. Hosted data follows Atlassian's Forge storage lifecycle.
- External catalog data must be handled by the operator selected by the customer.
For an app-data or privacy request, contact support@fogsea.top to confirm the applicable scope and available process. Never email live credentials.
Policies
Read the Privacy Policy, Terms of Use, and Data Processing Addendum.