DetailBridge support

• Support: support@zfinia.com. Include your site URL, the mapping (source Detail → Jira field), an example request key, and the status message shown on the DetailBridge page.
• Security issues: support@zfinia.com, with "Security" in the subject.
• We aim to reply within two business days. Support is best effort; there is no uptime SLA, because the app runs on Atlassian's platform.

• Install DetailBridge from the Atlassian Marketplace. You need to be a Jira administrator.
• Open Jira settings → Apps → DetailBridge, or Manage apps → DetailBridge → Configure.
• Choose Add mapping, then pick Customer (the request's reporter) or Organisation (the request's organisation).
• Choose an existing Detail field. Unsupported types are shown but can't be selected.
• Choose one or more service projects. This is required: DetailBridge never applies a mapping site-wide.
• Confirm the Jira field name, then choose Create mapping. DetailBridge creates a read-only Jira field, adds it to the projects' screens and fills it in on existing requests.

No field IDs, API tokens, personal credentials or URLs are needed.

Values refresh when relevant Jira requests are created or updated, through an hourly reconciliation, or when an administrator runs Sync now.

Changing a Customer or Organisation Detail does not notify apps, so a changed Detail reaches existing requests at the next request update or hourly run. Sync now applies it straight away.

• Text, single-select, email, URL and phone Details → text field.
• Number → number field.
• Date → date field.
• Multi-select, checkbox and Assets object Details are not supported yet.

• Read values with smart values, for example {{issue.Support Tier}}.
• React to changes with the Field value changed trigger. DetailBridge's updates fire it.
• Test values with a JQL condition, for example "Support Tier" = "Platinum" or ARR > 100000.
• Jira's generic Work item fields condition may not list Forge app fields. Use a JQL condition instead.
• Number smart values render with a decimal, for example 480000.0. Use Jira Automation's number formatting functions if you need a different format.

• Why hasn't a changed Detail appeared yet? Atlassian does not notify apps about Detail changes. Wait for the next request update or the hourly run, or choose Sync now.
• Why was a request skipped? It could belong to more than one organisation, so DetailBridge does not guess. Set a single organisation on the request.
• Why is a value empty? The customer or organisation has no value for that Detail, or the reporter is not a customer.
• Does DetailBridge store our customer data? No. It stores its configuration and sync counts only. The values live in your Jira fields.
• What happens if our licence expires? Syncing pauses. Mappings and existing field values are kept unchanged, and syncing resumes when the licence is active again.
• What happens if we uninstall? Jira removes DetailBridge's fields and their values with the app. If you reinstall within 30 days, Jira restores them; re-add your mappings with the same field names and DetailBridge reuses the existing fields.
• Can I delete a mapping and keep the values? Yes. Deleting a mapping stops updates. The field and its values remain until you delete the field in Jira settings.

Privacy policy: zfinia.com/detailbridge/privacy. Terms: zfinia.com/detailbridge/terms. Data processing agreement: zfinia.com/detailbridge/dpa.