sync 2 JIRA Instance in specific condition

Hi , 

need the help of experts here . 

we are planning to syncto 2 from 2 organization . customer and vendor . but we just want to sync these 2 project when component is "XXX". meaning that if component is not "XXX", sync option should be skipped . 

the reason for this syncing is : 

but us (as customer ) and one of our vendors are using JIRA . so there are  duplicated case which needs to be updated in 2 places , both in our JIRA and our vendor . I have been looking in to one of the sync plugin . but not sure if it is possible to define the condition of syncing based on "Component". I have noticed that the syncining condition was based on "Status" and "Issue type".

any one can help? 


3 answers

1 accepted

Hello Negar,

If you are using Exalate as your synchronization solution you can configure it to make it work that way. You would also be able to pick when exactly you want an issue to be synchronized on the other side (maybe you would prefer to synchronize when an specific transition is performed).

Exalate is configured through scripting. You write scripts to define the business rules of your synchronization: when a change goes from your system to the remote one and the other way around.

When you receive a synchronisation from the other side ("Create Processor" script), you can decide if ignoring this or not through the script:

if(replica.components.find { == "Component Name"} != null){
        //Update logic comes here


If you need any help with configuring exalate plugin, please contact me through the support channels (


Juan Grases

Hi Negar,

if I understand you correctly, you want to sync issues between two projects only if the ticket belongs to a specific component.

It is possible to sync issues like this with our sync solution - Backbone Issue Sync for JIRA. You can simply filter the issues to be synced by specifying a JQL, e.g. "component = 'Component A'".

For more information how to configure it, you can read our documentation or get into touch with our support team.

I believe, the other sync solutions also have these filter mechanisms.



Similar solution based on JQL is in IssueSYNC.
Or if you like you can replace automatic trigger with on demand trigger (simply button/action to create given issues on remote JIRA).
Another option is to synchronize based on workflow transition - for example, when the issue reach '3rd line support' status. 



Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published yesterday in Jira

5 ways you can make the most of Jira Software and Bitbucket Cloud

As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...

53 views 0 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you