Changelog
Release 1.1.0 · Forge 2.1.0
Cross-Site Sync administration and panel have been redesigned to make setup and troubleshooting easier. The upgrade from version 1.0.0 is direct and does not require reconfiguring connections or rules.
Features
- Overview page with setup steps, connection health, and items that need attention.
- Redesigned connection and rule management, with autosaved drafts, search, filters, and actions to manage or simulate rules.
- Rule wizard with space and work type selectors, mapping preview, per-direction policies, and simulation before activation.
- Operations to review links, check errors, edit mappings, and retry syncs; settings for retention, expiry notices by email and in Summary, and concurrent jobs.
- Panel actions to escalate, review errors, send comments, and control syncing.
- Workflow validator to check required fields, and a configurable post function for selecting the active rule.
- Native Jira remote link on both work items and detection of deleted remote work items.
- New attachments covered by the All new policy are copied, including those added after escalation. Attachments cited in comments are copied before the comment is posted and linked from it.
Scope and limitations
- Later field changes are not synced continuously, and remote status changes do not transition the local work item.
- Synced comments and attachments cannot be edited or deleted, and deleting the source attachment does not automatically delete its remote copy.
- Transferred images are attached to the destination work item; they are not displayed inline in comments.
- The panel does not offer a complete unlink-and-relink flow: it has no Unlink action, and pausing does not remove the link.
- The app sends data to the remote site and is not Runs on Atlassian.
- Jira Data Center, Confluence, OAuth 2.0 (3LO), creating work items from the remote site, a historical metrics dashboard, activity log export, a Marketplace listing, and license management are not included.
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.