FAQ
Clone tickets between two Jira cloud instances
If you want to copy some tickets to another Jira instance, we probably would recommend using Bulk Synchronization feature which is only for IssueSYNC Server: (https://deviniti.atlassian.net/wiki/spaces/SYNTWO/pages/771391762/Bulk+Force+Calculated+CF+ReSync#Bulk,ForceCalculatedCF,ReSync-Bulksynchronization)
However, this feature can be simulated in cloud too. Here what you should do:
- Change workflow in “old” Jira by adding temporary transition from given status to itself.
- Use custom event on this new transition.
- Set your event in create trigger (https://deviniti.atlassian.net/wiki/spaces/SYNC/pages/111317046/Triggers) .
- Execute bulk transition.
- At this point tickets should be replicated in other Jira instance if configuration was done properly.
- Remove temporary transition / cleaning configuration.
What is the communication protocol between JIRAs?
Communication protocol between JIRAs is http/https.
How issues are connected with each other? What about the key?
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).
Can we update existing issues, or does synchronization affect only new issues?
Depending on configuration synchronization can:
- Only create issues from JIRA-ONE to JIRA-TWO
- Create and synchronize updates from JIRA-ONE to JIRA-TWO
- Create and synchronize updates from JIRA-ONE to JIRA-TWO and JIRA-TWO to JIRA-ONE
So basically, different scenarios are possible.
We'd like to specify multiple issue types per contract. Is it possible?
Yes, it is possible.
One JIRA is Server and the other JIRA is Cloud. Would this be a problem?
It might be. We do provide functionality of synchronizing issues between JIRA Server ↔ JIRA Cloud but there are some limitations.
Be aware of that IssueSYNC for JIRA Server provides more features, which can not to be replicated in JIRA Cloud. The problem is JIRA Cloud does not allow to manipulate data in such a range as JIRA Server.
Contract setup also looks a bit different.
You are free to synchronize issues (fields, workflows, comments, attachments)
My changes are not synchronize while other users are. What is wrong?
There can be two simple reasons of such situation:
- Your username is used as Technical User (see Connection configuration), and so your changes are not synchronized by design.
- There is a query in Contract configuration that filters your issues out.
Technical user cannot modify existing issues in selected project!
Technical user must have all permissions for project, so please grant this permissions to Technical User.
I do not see remote contract, so I can not finish local contract setup!
In order to see remote contract, administrator or remote JIRA instance needs to provide "
Can I Synchronize worklogs?
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.