You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Join now to unlock these features and more
We are planned to share some tickets among our Jira and external's Jira. I'd like to know what's the best way or tool to do it. I found Exalate and Jira Jira issue sync, but I want to know your experiencies with them or if you know a better way to do it.
Hi @Jesús C_ ,
This is Dhiren from Exalate.
Exalate, provides a fully bi-directional synchronization between Jira(Cloud,Server,Data Center) and Jira(Cloud,Server,Data Center) among other ITSM systems that is fully customizable. It is easy to set up and the entire customization can be configured using a no-code interface. It also provides a Groovy based scripting engine for limitless customizability.
You can even integrate between Jira Software, Jira Service Management (Service Desk) and sync issues inside projects back and forth to achieve your integration requirements.
Exalate provides a flexible synchronization engine such that issues are automatically and securely synced - between multiple Jira's - wherever hosted. Benefit from a unified view and integrated workflow!
Use cases supported:
If you would like to see a customized demo of the product in action, feel free to book a slot with us.
Hello @Jesús C_,
As mentioned in the previous answers, two Jira instances can be integrated by a third-party integration solution providing true bidirectional synchronization with reliable and predictable synchronization outcomes.
OpsHub, an Atlassian partner, provides a no-cost Community Edition available that integrates standard entities. The Community Edition is rich enough for small deployments. You can download it and have a look if it meets your requirement. OpsHub’s Commercial Edition additionally supports the integration of more advanced data.
Before you start evaluating third-party integration solutions, you need to finalize your integration requirements, E.g., Entities to be synced and data fields to be mapped. When you are clear about your requirements, you can start evaluating the marketplace options available for Jira to external Jira integration.
The following evaluation criteria can be considered during the evaluation of third-party Integration Solutions.
Please reach out to OpsHub’s integration experts for an initial free consultation on integration planning.
Hi @Jesús C_
I'd recommend to check out the list of "issue sync" apps in the Atlassian Marketplace.
Since I'm part of the team behind Backbone Issue Sync, I'm obviously biased and won't try to give you a recommendation. But I can give you a couple of thoughts you should keep in mind:
After you've developed that plan what you want to synchronize, you could start trial version of the various apps you'd like to evaluate and see which one fits your needs the best.
Hope that helps,
@Jesús C_ I understand. What is the budget you have in mind for your integration? We have flexible options depending on the use cases. If you're willing to explore this as an option, we can still have the demo meeting. We'll get into the details of your use case and discuss ZigiOps as a solution (capabilities and pricing options).
@Jesús C_ hello! If you're looking for a fast and secure connection between the two Jira instances, take a look at ZigiOps. It's a no-code integration tool. It allows for customization to cover a wide variety of use cases. ZigiOps works bi-directionally - syncing the two Jiras and keeping them up to date in real-time. You can choose what data to transfer between them- incident, task, bug, story, issues, tickets, etc. Feel free to look at it and book a demo - if you want to see it in action.
Regards, Diana (ZigiWave)