The two-way sync between Jira instances is what sold us, and it genuinely works as

advertised. We collaborate with two external partners and before exalate we had

someone manually copying updates across projects every single day. Embarrassing to

admit but that was our actual process. Once we set up exlate the synchronization just

runs in the background comments, status changes, attachments everything stays

aligned without anyone having to babysit it. The field mapping configuration is flexible

enough that we could control exactly what gets shared with each partner and what stays

internal, which was a non-negotiable for us from a data privacy standpoint. Setup took a

bit of time upfront but the exalate team was responsive and helped us get the mappings

right. Review collected by and hosted on G2.com.

Honestly the initial configuration is not something you can figure out in an afternoon,

especially if your Jira setup has a lot of custom fields and workflows. We hit a few edge

cases where certain field types weren't syncing the way we expected and we had to dig

into the mapping rules to troubleshoot. Documentation is decent but could be more

detailed on advanced scenarios. Not a dealbreaker at all, just something to be aware of,

plan for a proper onboarding window rather than assuming you can flip it on in a day. Review collected by and hosted on G2.com.

I value Exalate for its ability to synchronize Jira issues with GitHub issues seamlessly, which is crucial in maintaining consistency between the private and public project views. This synchronization ensures that my team can focus their daily work within Jira while simultaneously providing visibility to our community and supported customers on GitHub, where they do not have direct access to Jira. Additionally, I admire the basic setup process, which is straightforward and allows for quick implementation, facilitating efficient initial deployment. Furthermore, after evaluating multiple vendors, I concluded that Exalate was the superior choice, confirming its effectiveness in fulfilling our specific needs. Review collected by and hosted on G2.com.

I find advanced scripting in Exalate challenging, especially when trying to implement more complex functionalities. Despite contacting support, I had issues syncing Jira fixversion with GitHub milestone, which required more than 50 lines of code and stopped working after a few months, leading to frustration and me eventually giving up on it. Additionally, I am not satisfied with the text rendering between Jira and GitHub, which I feel needs improvement. Review collected by and hosted on G2.com.

We've been using Exalate to synchronize tickets between Zendesk and Jira, and the experience has been smooth and highly effective. What truly stands out is the flexibility and control it provides — from intuitive visual triggers to more advanced scripting options that allow for precise and customized sync logic. Review collected by and hosted on G2.com.

for someone new to Exalate, the setup can be a little confusing at first. And sometimes, the error messages aren’t very clear, which makes troubleshooting harder than it should be.

But overall, once everything is set up, it works really well. Review collected by and hosted on G2.com.

Once you understand the outgoing/incoming sync set up for both programs, it is pretty straight forward in coding the changes. I leverage ChatGPT, Exalate's AI and a third party partner to complete our integration. Review collected by and hosted on G2.com.

As I chose the 'code your own' option, the one thing that initially hit us was our nuanced set up of Azure DevOps. Some custom fields weren't mapping so we ended up leveraging Bit2Bit to help us get across the finish line. Experience is key. Review collected by and hosted on G2.com.

I like the most in the quick relation between Zendesk and Jira for creating tickets that needs support from the engineering team. Review collected by and hosted on G2.com.

The configuration is a little tricky but not impossible. Review collected by and hosted on G2.com.

What stands out most about exalate is the support and custom AI tool that helps you code ( if you choose for script syncing) and set-up syncs incredibly fast Review collected by and hosted on G2.com.

We haven't had any issues yet with exalate itself if there would be one "dislike" that would be the need of a license on both the source and destination side however with a new Exalate networks this is off the table and no longer the case Review collected by and hosted on G2.com.

It is rapid to integrate two ITSM systems and have granualar control what is getting send and how the received information is getting applied. Review collected by and hosted on G2.com.

In my opinion I have not had any bad experiences yet with Exalate Review collected by and hosted on G2.com.

It is very flexible. I could implement practically every scenario I wanted because I was not limited by the interface. It is script based but there are so many ready to use scripts in the documentation that it is not a problem if you do not know the groovy scripting language. Review collected by and hosted on G2.com.

If the sync gets stopped it is hard to identify the reason just by reading the error log. Maybe some kind of filtering would be helpful. Also, sometimes the sync stops without any reason and then you need resolve and retry a connection. However, notifications about it can be configured. Review collected by and hosted on G2.com.

It really helps to cut down on repetitive work by automatically creating the Jira ticket from Zendesk.

We have Exalate in our Zendesk support ticketing and use it with Jira. Review collected by and hosted on G2.com.

Exalate tends to go down randomly pretty often. Never for very long, but just long enough to ask colleagues, "Anyone else having issues?" you get a few yesses and then it's working again. Review collected by and hosted on G2.com.

Easy to start using, you can create the first version very quickly and see the results.

Great support Review collected by and hosted on G2.com.

No filtering options in connections/triggers

When updating connections the order of connections in the list is changed and it's challenging to follow up on what connection you already updated and what is still left.

Error messages are console messages and users without experience can't easily understand what's the error about. Review collected by and hosted on G2.com.