Can the server in two different Geo-locations serve only one JIRA instance?

[Selahattin G]

Here is the situation: We have one JIRA Server instance and server in European location. But now, we have a team in China . Hence China Team needs to access same JIRA instance. But their access to JIRA is very slow due to their location. Is it possible the server in two different Geo-locations serve only one JIRA instance or any other solution? I know Data-Center not a solution.

Thanks.

Best regards.

[Stefaan Quackels]

Hi @Selahattin G,

I'm Stefaan from the Exalate-team Nic mentioned. This indeed is a common use case for synchronization.

It will come down to you setting up the instances as "mirrors" through real-time synchronization. You can choose what projects to sync.

Exalate can work for you straight out of the box. But it also offers great flexibility through scripting functionality.

So you can even resolve the issue mentioned where users would be modifying paired issues at the same time. This could be handled with some custom scripting.

Here is a video to see how to synchronize projects: https://youtu.be/U7dzYzwyL30

Anyway, hope this helps. Reach out to us if you have any questions at all (support@exalate.com). Or you can directly set up a one-on-one video-call for us to show you how Exalate would work for your use case here: https://www.idalko.com/exalate-book-demo/.

Cheers,

Stefaan

[Nic Brough -Adaptavist-]

No.  Not because of the geography but because a Jira Server can only run once.  One database and one application. 

If you want more than one node, you have to move to Jira Data Centre.  But this will not help you here either - although in theory you can have nodes geographically separated, in practice this does not work at all (Yet.  Atlassian have said they want to do it, but there's no schedule for it)

You'll need to think differently about this.  I would set up a new empty Jira server for the Chinese team, local to them so they have better speed.  Then I'd decide which projects I wanted to share between the two locations, and choose one of the synchronisation add-ons to replicate the parts I wanted.  With the most simple setups, you can just replicate a project (or set of projects) like-for-like, but the add-ons allow more flexibility (so user mappings, having different workflows at either end, selective comment sync and so on).  The synchronisation itself will still be slow, but it won't affect your users unless you have two people updating the same issues at the same time on both ends (and even then, the software will try to handle it gracefully)

I've had a lot of success with K15t's Backbone, and used Exalate in other places.