how to link 2 jira instance (hosted in different mode)

[Carolina SILVA]

We have been acquired by a company that has its Jira instance in Server mode
and we have our instance in cloud

We have some projects and security levels already in place, and this needs to be kept isolated

1. How can we link only 1 project (maybe more later), through our 2 instances?
2. What do we need to check before linking 1 project on 2 different instances?
- workflows
- custom fields?
- ....?
3. Does it exist a full process to analyze steps by steps? 
4. Are we obliged to install an external app?

[Dhiren Notani_Exalate_]

Hi @Carolina SILVA ,

Thanks for asking your question on the community, I am Dhiren from the Exalate Team.

I would recommend you to try out Exalate

Exalate is a bi-directional integration solution which supports all the hosting options of Jira (Cloud, Server, DC). You can choose what projects to sync and also choose what Issue Types & Fields to map!

It is very flexible and you can even map the status workflows; so there is no need to keep them exactly same as each team might be familiar with their own workflows.

The solution provides you a Groovy based scripting interface which is very customizable and you can even use advanced functionalities like httpClient() and make use of the REST API's provided by Jira.

Do let me know if you need more help and I can answer any more questions that you might have.

Thanks, Dhiren

[Nic Brough -Adaptavist-]

I would very strongly recommend using an app.  Synchronising two Jira systems is very complex, and trying to build something yourself is a massive undertaking.  It's going to cost you a lot more to do that work than it is to licence an app to do it.

I have done a simple version of a sync several times, always with Scriptrunner because that reduces the amount of work I'd have to do if I wrote an app.

Believe me, I've seen how much work @Matthias Gaiser _K15t_ has had to put into Backbone, and I know it is similar for @Dhiren Notani_Exalate_ 's team.  These do far more than I've ever achieved with Scriptrunner, a lot more easily and I've used both of them in many places.

There is another option now, we (Adaptavist) wrote Scriptrunner-Connect to enable and enhance connections between many Atlassian systems, and of course, it can do Jira to Jira.  It is also independent of them - you don't need to install anything on either side of a connection, just give it access to your systems.

[Carolina SILVA]

I all,
thanks a lot for your help

I would like to know if I can do it without app?
As the cost is massinve because app will need to be installed on both instance.

* Is it possible to Create a new link on Application links?
* If yes, what to I need to know before doing it? As I dont want to mix up all issues/ all projects but only link 2 projects and maybe more but later 

thanks  

[Jack Brickey]

Not really no. You could use create issue by email and could consider adding issue links in the description or comments. You could play around with automation to try an improve linkage. However all of this is not reliable or scalable. Of course there are the APIs which you could use to creat your own backbone sync.

[Matthias Gaiser _K15t_]

If you want to do it without an app, I'd look into Automation with Web triggers and web requests. The basic idea is:

• When an issue is created in Jira A
  • send a web request to a webtrigger of Jira B
• When the webtrigger in Jira B is called
  • create a new issue Jira B
  • set a custom field to the issue key of Jira A (to identify which issue needs to be updated)

If the issues get updated later, you can do it in a similar way:

• When an issue is updated in Jira A
  • send a web request to a webtrigger of Jira B
• When the webtrigger in Jira B is called
  • perform a JQL with the customfield = Jira A issue key
  • update the issue

You can try if this manual handling is enough for you. If it isn't, you can of course also implement your own scripts using the Jira REST API.

Or maybe still consider using an issue sync app - up to you.

[@Akshithrekulapelli]

Hi,

we are trying to link issues between two different JIRA instances based on the custom field value. 

[@Akshithrekulapelli]

We have a Custom field in JSM project where it stores JSW issue key. we want to link JSM and JSW issues using automation. how to compare JSM project custom field and JSW issue key in order to link both issues.

[Matthias Gaiser _K15t_]

@Akshithrekulapelli - I replied on your other question to have the discussion in a separate thread.

[Matthias Gaiser _K15t_]

Hi @Carolina SILVA

if you talk about linking 1 project, do you mean you want to synchronize the changes between both Jiras? If that's the case, I'd also recommend Jack's advice to install an issue sync app.

With such an app, you can define various rules which projects or issues within a project you'd like to synchronize. You can then further decide which fields of the issue you'd like to synchronize and which ones not. There's no need to have the same custom field or workflow on both sides - you only need to be clear how you want to map the values to each other. I'd recommend to start a free trial to get a feeling how this may work.

I'm part of the team behind Backbone Issue Sync and all of the above is true for Backbone and in general also for the other issue sync apps.

Since you can't buy new licenses for Server Apps, you'd need to get a Data Center license for Backbone which also works without problems.

Cheers,
Matthias.

[Jack Brickey]

Hi @Carolina SILVA ,

for this you would need to consider an add-on application such as backbone sync. However, given the eminent EOS for server, I am unsure if you will be able to install such an application on the server side. In any event definitely check the marketplace for appropriate solution