items syncing between jira instances

[jla stats]

I have licenses for 1200 users at my workplace rn. Moreover, almost 300- 400 users use jira  apps/plugins. However, I have to buy 1200 licenses with same features. 

Is it possible to set up 3 instances, individual instances for QA, dev  and JSM with different licensing types. Moreover, would jira be able to sync data between all these instances in real-time?

[Umer Sohail _K15t_]

Hi @jla stats , thanks for the question. I am the PMM for Backbone Issue Sync for Jira.
Thanks, @Ankit Srivastava for mentioning our app! 

Unfortunately it is not possible to sync issues between different Jira projects in real time without a 3rd-party app. Good new though, a specialized Jira Issue Sync app like Backbone Issue Sync for Jira can help you do just that!
 
Using Backbone, you can sync Jira issues and the corresponding data between all three of your Jira projects in real-time irrespective of the licensing type. This includes syncing Jira fields (including custom fields), comments, workflows, and attachments without ever leaving your own Jira project. 

Best of all, you can do this on Jira Software, Service Management, or Work Management projects on Jira Cloud, Server, or Data Center.

In case you're interested in learning more, feel free to schedule a free demo 
or try Backbone for free for the first 30 days!  

[Riley Venable]

It is possible to set up three instances with different licensing types, but Jira may not be able to sync data between all these instances in real-time.

[Ankit Srivastava]

Hi @jla stats 

Welcome to the Atlassian Community!

Hope you are doing well.

Please use the Backbone Issue Sync for Jira plugin:
https://marketplace.atlassian.com/apps/1215199/backbone-issue-sync-for-jira?tab=overview&hosting=cloud

You achieve sync of Jira instances with this plugin.

Thanks
Ankit Srivastava

[Brad Peterson]

Hi @jla stats 

OpsHub, an Atlassian partner, provides a free Community Edition that integrates all issue types between two Jira instances. OpsHub Community Edition provides rich integration capabilities, like:

1) Integration Richness: In addition to integrating all basic fields, it also integrates attachments, web links, comments, mentions, links, and inline images.

2) Scalable: It takes care of sync load by ensuring that even during peak hours, Jira server is not impacted by sync operations.

3) Field-level Conflict Management: It enables you to define a conflict resolution policy when data in two Jira instances contradicts the updates coming from another instance.

You can get started immediately with OpsHub’s Community Edition without requiring any call or license.

You may also reach out to OpsHub's  integration experts for an initial free consultation on integration planning.

[Diana_Architect_ZigiWave]

@jla stats hey there! As already mentioned, it's absolutely possible to sync your Jira instances. Still, you'll probably need an additional tool to help you connect/sync the data between them and keep them updated in real-time. The Atlassian marketplace might provide help - you can find tools that can help you with synchronization. Such a solution is ZigiOps. It's a 3rd party one, fully no-code & customizable to fit different use cases. It will connect the Jira instances, sync their data and keep the up-to-date. Feel free to look at it and if you want to see how it can execute your use case - book a demo (it's free & non-binding).

Regards, Diana

[Syed Majid Hassan -Exalate-]

Hi,

A very warm welcome to the community. This is Majid @ iDalko. 

So, it is very possible to have three distinct Jira instances logically divided by business function, but it all depends on how much collaboration is required here. Would you end up having users accessing each others instances in order to get the full picture. If this is the case, you will end up paying for an integration solution such as Exalate in order to keep the issue in sync - and that would again add to the cost that you are trying to save in the first place. 

Bottom line - you will need to do some costing and see if an integration app would work out cheaper than paying for a higher Atlassian base license!

Thanks

Majid

[Katarzyna Szumilas_Deviniti_]

Hi @jla stats

In principle, it's possible to have different teams working on separate Jira instances and still be able to cooperate successfully. Efficiency here depends mostly on the kind of data you wish to exchange between the teams.

There are a few Marketplace add-ons that automatically create and synchronize tickets (their fields, comments, attachments, etc.) between multiple Jiras. The synchronization is instant- it might take just seconds or a few minutes, depending on the tool.
My team is responsible for two of such plugins - Issue Sync for Jira and Issue Sync Lite - the second one is brand new and what might be important in terms of multiple licenses - it's free! :) 

If that sounds like a solution, you can give it a try or book a free demo via Calendly.