How to sync issues between multiple JIRA Cloud instances

[Bill Hall]

We are planning to implement a JIRA Cloud instance and will need to sync issues between our instance and vendor instances (cloud and/or server -based).

The add-ons I've located for conditional syncing, such as IssueSync and Cross for JIRA, all seem to be server based.

So, I'm wondering if:

a) are there any cloud based options?

b) are there any stand-alone options?

c) or do we have to stand up a JIRA Server instance just for the sync plugin?

Thanks

[Tobias Anstett _K15t_ · Accepted solution]

Another add-on you might want to take a look at is Backbone Issue Sync for JIRA.

a) you can download it for server, data center and cloud - it provides integrations in all directions.
b/c) Backbone is installed on each instance as an add-on

For more information check out the Marketplace Listing and the documentation.

[C]

is there a way to pull the full history of a ticket?

[Matthias Gaiser _K15t_]

I imagine by pulling the full history, you want to have the same history on the target issue as in the source issue, right?

What Backbone does, it applies all changes on the target issue. As soon as the source issue is changed, the target issue will be changed and therefore a similar history in the target issue will be produced - however the change dates/times will be different.

However, the initial history (before the sync) will not be reproduced on the other side.

I assume, you already know that. If you want to discuss your use case with us further, please let us know at support@k15t.com and we arrange a meeting.

[francis]

And Exalate is another serious offer

• Supports Cloud to Cloud synchronisation (next to Server/Cloud and Server/Server)
• Doesn't require a standalone server

More information can be found at 

• Marketplace listing
• Documentation site

Francis

[Rafael Sanchez Alfonso]

Would exalate require software installed on both cloud instances? Ideally I would like to minimize changes on one of the cloud instances (the one owned by our client). Sincerely

[francis]

Exalate requires to have it installed on both sides.  The reason is that you want to remain autonomous between the two systems.

Whenever your customer is doing a configuration change, you don't want to be affected or the way around.

There are solutions to do the synchronisation from one side, but that is an approach which will get problematic whenever you scale the number of connections.  Imagine that you need to negotiate with all your partners that you plan to change your workflow.

With an autonomous solution like Exalate, configuration changes are contained on one side as long as the information sent to the other partners is not changed.

Francis

[Marcin_Kokoszka]

There is another app you might want to check out: Issue SYNC - Synchronization for Jira.

You can also use it to sync your data between Jira Cloud, Server or Data Center regardless of the type (Core, Software, Service Desk). 

[Jobin Kuruvilla [Adaptavist]]

Take a look at ConnectAll. This has to be installed on a standalone server but it can sync issues between two cloud instances.

[Jobin Kuruvilla [Adaptavist]]

Just to be clear, you don't need a JIRA server instance for it. ConnectAll is installed as a separate application.