I'm looking to sync 2 projects in different jira cloud instances. We want to be able to create or work on an issue that appears on both instances.
I've done an application to link to separate issues, but this is not the solution we are looking for. We are also looking for a way that doesn't involve an additional app as much as possible. Thanks!
Hi @Anthony Alberto ,
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.
Thanks
Dhiren
if you search for a way to do it without an additional app, I'd recommend to checkout Jira Automation to see if that meets your needs.
However, that would be quite some manual work. That's why I would encourage you to check out the various issue sync apps on the Atlassan Marketplace. I'm part of the team behind Backbone Issue Sync. If you want to discuss your requirements with us, let us know via help@k15t.com.
My idea about using Jira Automation
If you decide to go this way, you can use the actions Send web request to send data from one Jira instance to the other. The other instance can then use an Incoming webhook trigger to take the data and perform the corresponding action.
Hope that helps,
Matthias.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Anthony Alberto and welcome to the Atlassian Community!
Maybe this other question could help you:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Anthony!
If Automation doesn't meet your use case here, I encourage you to give a try my team's brand new application Issue Sync Lite.
It's free and quick to set up and maintain. It doesn't require coding or complicated manual work and allows you to securely connect two Jira Cloud instances and automatically create synchronized issues in both of them.
With Lite you can sync multiple projects and issue types, as well as custom fields, comments, and very soon - attachments.
If that sounds interesting, let us know via Calendly and we will be glad to show you the tool during demo.
Best regards,
Kasia from Deviniti
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kasia
will this issue sync lite application free for trial period or it is really free? It sounds like something that we can use for our bidirectional sync needs between the two Jira cloud instances
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
The app is totally free (for all user tiers, not only for the trial period) :)
Cheers,
Kasia
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sure thing! The app can be downloaded from here.
You can try it out directly on your instance or book a meeting with our support team that will demonstrate the app's possibilities.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I used Jira Automation to do it.
Summary:
{{webhookdata.fields.summary}}
Description:
{{webhookdata.fields.description}}
Other fields:
I put issue key into labels and add Epic Link.
{
"fields": {
"labels": [
"{{webhookdata.key}}"
],
"customfield_10011": "{{webhookdata.fields.customfield_10011}}"
}
}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, how do you manage the transitions in the issues using this workaround? It is possible to transition a isssue in the instance B, when the issue is transitioned in the instance A?
Thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Anthony Alberto hello! Not using an additional tool will, indeed, require manual work. If you, however, decide to use a 3rd party tool, check out ZigiOps. It's a no-code integration platform than can connect the two instances in minutes and sync them (with the data/fields you want). It has advanced field mapping and allows for customization - to cover various use cases. Feel free to explore it and book a demo, in case you want to see it how it can solve your use case.
Regards, Diana (ZigiWave)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.