Skip to main content
Version: 2.1.0

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, use the account ID of a valid remote account as a fixed value; you cannot use a local user field directly as the source.

Are field changes synced after escalation?​

No. The rule maps fields when it creates the remote work item, but it does not continuously sync later field changes or convert the remote status into a local transition.

Not as a complete flow from the panel. The interface does not provide Unlink; Relink only appears when a link is already Unlinked, a state you cannot reach from the panel. Pause sync does not remove the link.

What happens if the remote work item is deleted?​

Cross-Site Sync detects that the remote work item is unavailable and shows an error on the link and in the panel. Review the details to decide how to resolve it.

Yes. When the remote work item is created, Jira adds a native remote link to both work items, in addition to the link managed by Cross-Site Sync.

What happens to attachments added after escalation?​

If the rule uses the All new policy, new attachments covered by that policy are copied even when added after the initial escalation. File size limits and blocked extensions still apply.

When a synced comment cites a file, the app copies the file before posting the comment and links to the copy. This also works for PDFs and other non-image files. Transferred images are attached to the destination work item but are not embedded in the comment.

Are comments written by the service account synced?​

No. The app does not import comments written by the remote service account again. Use a dedicated service account for the connection, and ask users to write comments from their own accounts.

Are token expiry notices sent by email?​

Yes. They are sent by email and appear in Summary. You can configure the thresholds in Settings.

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.

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, and a message. The retention period is configured in Settings. It does not store comment text or attachment content.

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.

What is not included in version 1.1.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, converting remote statuses into local transitions, editing or deleting synced comments and attachments, inline images in destination content, activity log export, a Marketplace listing, or license management.