nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira integration with other organization.

Dhananjay Kumar_4pq4ez

Hi Team,

We have one client who have their own Jira subscription for their organization. However, as we manage their services. We need to get the tickets on Jira of our organization.

Please help me with the ways to integrate our organization Jira with their Jira desk, so that we can get the ticket on our jira whenever they raise the ticket on their jira. Also, if a comment is updated from our side, it should reflect on their ticket and vice versa.

Thanks in advance.

Accepted answers

All comments

Pramodh M

Hi @Dhananjay Kumar

There are couple of ways

First way - Automation

First create the integration via Application links which will help you in linking the tickets

Then create the webhook automation and logic from both sides to sync the issue with comments

This would require manual work to define the logic and check the fields you want to sync with validation to edit the corresponding issue in the other instance

Second way - plugin

you can use exalate plugin to automatically sync the issues in unidirectional way or bidirectional way

https://marketplace.atlassian.com/apps/1213645/exalate-jira-issue-sync-more?tab=overview&hosting=cloud

Thanks,

Pramodh

Matthias Gaiser _K15t_

Hi @Dhananjay Kumar

to complete @Pramodh M's answer: There are a couple of issue sync apps available in the Atlassian Marketplace which are designed for this use case to synchronize tickets between different Jira instances.

These apps allow you to configure which tickets and which fields you'd like to synchronize as well as if attachments or comments should be included, and many more features.

I'm working for the team behind Backbone Issue Sync. If you want to discuss your specific use case with us, let us know via support.k15t.com

Cheers,
Matthias.

Syed Majid Hassan -Exalate-

Hi @Dhananjay Kumar ,

This is Majid @ Exalate.

The use case of Jira-Jira bi-directional synchronization is best served using an integration app such as Exalate. The app provides you fully customizable synchronization between the two Jira instances with the ability to go as granular as you like.

Please feel free to book a customized demo if you would like to see the product in action.

Thanks

Majid

Diana_Architect_ZigiWave

@Dhananjay Kumar hi! A bi-directional integration will do the real-time ticket synchronization between your two Jira instances. If you're open to using an external tool to help you with this, take a look at ZigiOps. It can be customized to fit various integration scenarios and can help you transfer/sync the data and fields you choose. Upon its deployment, the tool will automatically sync and keep up to date the two Jiras so a change in one of them will immediately show up in the other. Take a look at it and feel free to book a demo if you want to see it in action.

Diana (ZigiWave team)

Diana_Architect_ZigiWave

Brad Peterson

Hello @Dhananjay Kumar,

The best way to integrate two Jira instances of different organizations, bi-directionally, is through a third-party Integration solution.

OpsHub, an Atlassian partner, provides a free Community Edition that integrates standard entities. It provides true bi-directional synchronization with reliable and predictable synchronization outcomes.

For Jira-Jira bi-directional integration, you can begin by defining your requirements and selection criteria to help you select the right integration approach and tool. The following are the key considerations as part of the selection criteria:

Integration Richness: It is very important to integrate complete information of Jira tickets on both Jira instances; For any information missed in the integration, data on Jira instances might be different and it gets unreliable and unusable, over time. Understand whether the tool can integrate the complete Jira ticket information such as attachments, web links, comments, mentions, traceability, and inline images.
Skill required: Some tools are a collection of unsupported beta versions of scripts, requiring a very high degree of sophistication. These can be highly time-consuming, error-prone, and can hinder operations. As part of the evaluation, analyze what part of integration may require script and involvement from your side.
Field-level Conflict Management: As this is a bi-directional integration, there is a possibility of data being updated simultaneously in both Jira instances. As part of the evaluation, analyze which tool supports field-level conflict management in such cases.

OpsHub’s Commercial Edition additionally supports the integration of more advanced data. Please reach out to OpsHub’s integration experts for an initial free consultation on integration planning.

Thanks

Brad

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-service-management-cloud

jira-service-management