Frequently asked questions
Do I need to install the app on both sites?
No. Install it only on the local site. On the remote site, you need a technical account with an API token and permission to create work items in the destination.
Why does the remote summary include the local key?
The rule must include the local key in the summary template, for example [{{local.key}}] {{local.summary}}. This identifies the source work item and helps prevent duplicates when an operation is retried.
Why do remote user fields only support a fixed value?
The app does not look up or automatically convert a user on the local site into an account on the remote site. To set the destination user, set the fixed account id of a valid account on the remote site as a fixed value; you cannot use a local user field directly as the source.
Are field changes synced after escalation?
No. Version 1.0.0 maps fields when it creates the remote work item, but does not continuously sync later field changes or convert the remote status into a local transition.
Do mentions notify people on the other site?
No. Mentions are converted to @Name text. Jira mentions are not created on the remote site, and those users are not notified.
Why is an image not displayed inline in a remote comment?
An inline image is converted to a reference such as [Attachment: file] and, if the rule allows it, sent as an attachment. Version 1.0.0 does not embed the image in the destination content.
Does a remote status change update the local status?
No. The app posts a comment on the local work item, usually within about five minutes. It does not run a local transition automatically.
What does the activity log store?
It records the operation, result, date, a message, and a correlation ID. It keeps up to 90 days of activity, depending on the settings. It does not store comment text or attachment content.
What happens if the remote work item stays in Done?
If it remains in Done for the period configured in the rule, the link is archived and the app stops checking the work item for status changes.
Is the app Runs on Atlassian?
No. Cross-Site Sync sends fields, comments, and attachments allowed by the rule to the remote Jira Cloud site, so it needs outbound network access to that site.
Can I unlink or relink a work item?
Not in version 1.0.0. You can pause and resume syncing, but pausing does not remove the link or let you connect it to another remote work item.
What happens with the “All new” attachment policy?
In version 1.0.0, this policy does not copy attachments added after the initial escalation. Attachments cited in comments can still be transferred if the rule allows it. File size limits and blocked extensions also apply.
What is not included in version 1.0.0?
It does not include Jira Data Center, Confluence, OAuth 2.0 (3LO), creating work items from the remote site to the local site, continuous field sync, status mapping to transitions, editing or deleting synced comments and attachments, unlinking or relinking, inline images in the destination, a metrics dashboard, activity log export, email notices for token expiry, a Marketplace listing, or license management.