Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Do I need to install Exalate to both source and destination instances?

I have a question with Exalate installation.


If I want to have one-way sync btwn two different instances, am I supposed to install the product to both instances? 

Or is it just OK to install the plugin only to the source instance (or maybe to the destination instance)?


Thanks in advance!

2 answers

2 accepted

@굠kang ,
Thank you for posting in the Community.

You will need to download Exalate in both Jiras.

Once you have created a connection between the two Jiras, you can select which way do you want the information to flow. It could be biderctional, A to B or B to A (you can also adjust the flow per field)

This guide should help you get it configured:


Let me know if this answers your question,

Jose Lobo
PreSales Engineer at Exalate

1 vote
Answer accepted

Hi @굠kang,

yes, your understanding is correct. You need to install Exalate in both Jiras - or did something change recently, @Exalate team?

If you haven't decided for Exalate yet and looking for this requirement, you could have a look into our solution Backbone Issue Sync which is offering a remote license model so that you don't need to install it on the other side. You can read a full scenario description how it works in our docs.

If you need additional help, our team is also happy to help you via


PS: If it wasn't obvious enough, I'm part of the Backbone Issue Sync team.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events