Changelog
Release 1.0.0 · Forge 2.0.0
First release of Cross-Site Sync for Jira. The app connects two Jira Cloud sites and is installed only on the local site; the remote site uses a technical account and an API token.
Features
- Remote connections with credential testing, token rotation, and expiry notices.
- Rules to choose spaces, work item types, triggers, field mappings, comment policies, and attachment policies.
- Dry runs to review the data that would be sent without creating the remote work item.
- Manual, transition-based, or field-value escalation, without duplicate work items for the same rule and local work item.
- Two-way comment and attachment sync according to the rule.
- Remote status change notices as comments on the local work item.
- A work item panel and administration for links, the activity log, and settings.
Scope and limitations
- Later field changes are not synced, and remote status changes do not transition the local work item.
- Work items cannot be unlinked or relinked. Pausing only stops syncing temporarily.
- The All new policy does not copy attachments added after the initial escalation; attachments cited in comments can be transferred according to the rule.
- The app sends data to the remote site and is not Runs on Atlassian.
- Jira Data Center, Confluence, OAuth 2.0 (3LO), creation from the remote site, editing or deleting synced comments or attachments, inline images in the destination, a metrics dashboard, activity log export, email notices about token expiry, a Marketplace listing, and license management are not included.
There is no previous version or upgrade path for this first release.