Yes, it’s necessary to have Issue Sync installed and active on all Jira instances that you wish to synchronize. Issue Sync on your local Cloud instance sends synchronization data that is being processed by our server and then passed to Issue Sync on the partner instance. In order to send, read and perform the requested changes, the plugin needs to be active on both environments.
You can purchase an app license in the name of your partner. To do so, contact our Sales Department at atlassian@devinti.com.
If you want to copy some tickets to another Jira instance, we probably would recommend using Bulk Synchronization feature which is only for IssueSYNC DC:
However, this feature can be simulated in cloud too. Here what you should do:
Communication protocol between Jiras is http/https.
If Jira-ONE instance has issue key ABC-XXXX, the Jira-TWO will not have exactly the same issue key. Issue key is generated from project key and sequence number. So it is more likely that in Jira-TWO there will be issue with key like DEF-YYYY.
However, issues are linked between instances so it is possible to reveal ABC-XXXX in Jira-TWO (and vice versa).
Depending on configuration synchronization can:
So basically, different scenarios are possible.
Yes, it is possible.
It might be. We do provide functionality of synchronizing issues between Jira DC <-> Jira Cloud but there are some limitations.
Be aware of that IssueSYNC for Jira DC provides more features, which can not to be replicated in Jira Cloud. The problem is Jira Cloud does not allow manipulating data in such a range as Jira DC.
Contract setup also looks a bit different.
You are free to synchronize issues (fields, workflows, comments, attachments)
There can be two simple reasons of such situation:
Technical user must have all permissions for project, so please grant this permissions to Technical User.
In order to see remote contract, administrator or remote Jira instance needs to provide “Create/Update triggers” in Outgoing configuration and setup Incoming configuration.
At the moment we do not provide such a functionality for Jira Cloud due to its limitations. We do plan to introduce this feature for Jira Cloud in the future.