Installation and requirements
Install Cross-Site Sync for Jira on the Jira Cloud site that will act as the local site. The other site, the remote site, does not need the app.
Before you start​
- A Jira administrator must install the app on the local site and configure its connections and rules.
- On the remote site, prepare a technical account with an API token and permission to create work items in the destination spaces. Grant any additional permissions needed for the data each rule will transfer.
- If your organization uses scoped tokens, select that mode when creating the connection and check that the account has the permissions required for the operation. The connection test helps identify missing credentials or permissions before you save.
- The app needs outbound access to
*.atlassian.netandapi.atlassian.comto communicate with Jira Cloud.
Install on the local site​
- Sign in to the local site with a Jira administrator account.
- Open the Forge installation link provided by the app administrator and select the local site.
- Review the requested permissions and confirm the installation.
- In Apps → Manage apps, check that Cross-Site Sync for Jira is installed.
- Continue with connecting the remote site.
There is no Marketplace listing. If you do not have the installation link, ask your Jira administrator or the team that manages the app.
Upgrade from version 1.0.0​
Upgrade directly to version 1.1.0. You do not need to reconfigure connections or rules, and app permissions are unchanged.
App permissions​
The app requests these permissions on the local site:
read:jira-workandwrite:jira-workto read and update work items.read:jira-userto read the user information it needs.manage:jira-configurationfor Jira configuration.storage:appto store app configuration.
The app also needs outbound access to *.atlassian.net and api.atlassian.com. It sends the remote site the information you allow in your rules. For this reason, it is not Runs on Atlassian.
Prepare the remote site​
- Create or choose a technical account on the remote site.
- Give it permission to create work items in the destination spaces and the permissions needed to transfer comments and attachments, as required by your rules.
- Generate an API token. Have the account email, token, token type, and expiry date ready, if applicable.
- Share these details securely with the administrator who will configure the connection on the local site.
The remote token is stored encrypted. After saving the connection, the interface only shows its last four characters; the full token is not displayed again.