Looking for Jira Issue Replication Solution Between Instances

[ejanis]

Hi All,

I have been looking for solution to replicate a project, and all its related issues, from my data center instance to a cloud instance.  All I can find for a total solution is Exalate or Backbone.  Backbone looks like it has too small of an installed base and has some negative reviews when it comes to product support, and Exalate is struggling to implement their solution that works with my data security requirements.

All I want to do is replicate a project from DC to cloud, when a DC user updates an issue field, that change is sent to a project (same name) in the cloud, and vice versa.

I have three separate businesses and they all have there own Jira instances.  I wish they could all share one, but that is above what I can control.

Seems like a simple use case but I am surprised with the lack of information out there - unless I am missing a crucial search term??

Any leads on other solutions would be greatly appreciated. 

Thanks in advance, Erik

[Syed Majid Hassan -Exalate- · Accepted solution]

Hi @ejanis

This is Majid @ Exalate. 

I think your initial research is spot on i.e. the two solutions identified would probably be considered as market leaders in the Jira Jira integration space. However, I am not sure about the security concerns you raise related to Exalate and would love the opportunity to discuss those with you. You can reply to this post with the exact security issues that you have identified or alternatively book a call with me here. 

Also, there is a lot of material on how to get started with Exalate, but I have picked this post for you to get started. Please let me know how it goes and if you need a hand with the setup. 

Thanks

Majid

[ejanis]

Hi Majid,

I am already working with an Exalate sales engineer and the hold up is in your engineering organization at the moment.  Why? I am not sure.

For the rest of the community, my challenge is that my data center instance resides behind a firewall.  The Exalate GCP server that is upstream from my firewall needs to initiate a conversation with my Jira server.  I cannot just whitelist a whole range of IPs from Google's cloud to talk directly to my Jira Server.  I need a specific host, or very small range of hosts, that I can allow to talk inbound to my Jira server.

Outbound server to server connection initiation is obviously not an issue, only the inbound.

[francis]

Hi @ejanis 

I'm Francis - Product Manager for Exalate.

There is no need to open any firewall port whenever using a private/public connection.  In this connection mode, all tcp connections are built from the Jira DC towards the node residing on the cloud.

Additionally - there is a procedure to ensure that all connections from the cloud based node goes over a single egress IP address (actually 3 of them atm)

Let me know what the ticket is.  There might be a miscommunication somewhere and I will help to clarify.


Francis

[ejanis]

Thanks for your response.  I do not have a ticket number, but I will email my SE your comments to see if we can speed things along.

[Matthias Gaiser _K15t_]

Hi @ejanis

I'm part of the team behind Backbone Issue Sync. I'm aware of the reviews you've talked about - and also of the circumstances of their situations. I can assure you that Backbone is running on customer instances reliably for around 10 years now.

Feel free to try it out yourself for free - or book a demo with us. Then we can also talk about your security requirements.

Alternative
If you don't like use these sync solutions, I'm afraid you'd need to do it yourself. You can try using Jira Automation or your own combination of scripts and webhooks which can use the REST APIs to read/write data.

Cheers,
Matthias.

[ejanis]

Thanks, Matthias.

I'll set up conversation to see if your product can meet my security challenges.

[Umer Sohail _K15t_]

Hi @ejanis ,  this is Umer, PMM for Backbone Issue Sync for Jira by K15t. Thanks for the question and mentioning Backbone!

I wanted to try and address some of your concerns regarding Backbone's user base and product support.

Backbone has been helping organizations, from conglomerates to start-ups, for 10+ years now. This aggregates to around 1200+ enterprises worldwide, and we boast an average of 3.5/4 star rating on the Atlassian Marketplace. 

As far as the support is concerned, our app's simple UI, quick setup, no coding requirement, and easy in-app troubleshooting make the need for support as little as possible. The app is also categorized as "Cloud Fortified" by Atlassian, meaning we guarantee 24hr response time for level-1 support, along with a high level of cloud security and enterprise-grade reliability.

Please visit our landing page to learn more, or simply reply here if you have more questions or concerns! 😊 

[Diana_Architect_ZigiWave]

@ejanis hi! I see a lot of options for you in the comments. :) I'll just add another one to the 3rd party - ZigiOps. It's a fully no-code solution that will connect your Jira instances, sync them and allow you to transfer/migrate just the data you want. No additional coding is needed & none of your data will be stored, if that's what you're afraid of. Also, there is no limitation to the amount of data you want to send from one instance to another. 

Feel free to check ZigiOps and book a meeting with our tech team just to learn more bout its capabilities. 

Regards, Diana (ZigiWave team)

[ejanis]

Hi Diana,

I looked at your product link, but I don't see any connector application that would accomplish bi-directional replication of issues between two Jira instances. 

[Diana_Architect_ZigiWave]

@ejanis  we're currently updating our website & the list of systems we provide integrations for. it will take more than expected to upload everything :). However, ZigiOps can make integrations between two instances of the same systems (Jira & Jira, SNow to SNow, Remedy to Remedy, etc).

ZigiOps can collect issues from multiple projects and report them to either multiple projects or a single project to the target system.
The tool needs "read" access (outbound connection) from the ZigiOps server to both Jira servers. No access from Jira to Zigiops is needed.
Feel free to drop us a line in our chat or save a demo slot so the tech team can explain and showcase how it can be done.