Exalate Reviews

It is rapid to integrate two ITSM systems and have granualar control what is getting send and how the received information is getting applied.

In my opinion I have not had any bad experiences yet with Exalate

Integrate two systems and have them be in fully bidirectional syncronization.

The multiple ways they offering about configuring syncing connections (manual, wizard, scripting). This is extremely handy!

Can't really find one downside on Exalate.

Exalate removes the syncing barrier between different Jira instances.

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.

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.

It connects two Jira instances so one of them can be put in front of a firewall and the other remains in a secured environment.

It can connect two teams in one Jira instance where outputs of one team can become an input for another team.

it saves a lot of effort when you want to synchronize issues between instances. Easy to set up and use and works as expected.

identifying issues under sync in jira cloud is not as easy as in jira server

syncing issues between instances (our own and clients')

The visual interface, although new is a good way to go. Easy to configure. There are bugs that I reported but once that is fixed, the product will be complete.

It did take some time to polish all bugs, but after that was done, it didn't require us to monitor anymore.

I strongly suggest you opt-in for professional services if you have time constraints.

Sales and support are excellent.

It takes some time to understand how the product operates. Definitely not a tool for quick fixes.

It will become a great product once all interface issues are solved. Before that happens you need to get into groovy scripting.

If you have simple tasks that you need to do, then you might consider Exalate. Using it across platforms (Zendesk, JIRA DC, JIRA Cloud) as I do is painful and not reliable at all. Errors are popping like Xmass lights for all kinds of reasons. Even if you make it work and for hours there is no a single Sync error, two days later you come back, there are 60 errors in the bucket. So it needs to be constantly monitored. Which goes into the reliability section.

Features are different, depending on the platform. For instance, Visual editor which is simple to use and which I do like is available in Zendesk -> Jira Cloud migration, but when you try JIRA DC -> Jira Cloud migration, this option is not available. You need to go with the script. So if you didn't have any contact with Groovy, now you will have to excel it. So definitely you should check if using something to do API calls instead of Exalate is something that is easier to set up.

Some of the bugs of the Zendesk component interface I've already reported so these need to be fixed. Limitations like the addition of the new fields you need to overcome.

Here is the explanation. If you create a connection using Visual editor and after you are done you want to add one new field to be synced, this is not possible without writing a script. It doesn't o refresh.

Also, system fields from Zendesk are not being synced so I cannot catch Zendesk Issue ID and place it on the JIRA ticket for reference. This is a problem when keeping track of issues you have in Sync!

I'm using Exalate to support migration from Zendesk to Jira Cloud and from Jira DC to Jira Cloud.

Important to mention is that I'm not using it to migrate issues! I'm using it to keep them in sync (unidirectional) until the cutover date. Another tool is being used for the actual migration of issues.

It integrates with a lot of different tools.

At this point I cannot say. It is too early for our project.

Integrating Jira and Service now. Saves time.

Oddly enough, Jira to Jira integrations and Jira to Zendesk Integrations require several API configurations even though there are native add-ons. Exalate has made it great to easily connect Jira instances even using the standard licensing and configure what fields/workflow-related items go-between project tickets for any cases you integrate.

There isn't much to say; the support has been great to get a hold of for user issues. You will need to contact the team that develops Exalate, not jira.

API integrations between multiple Jira instances for managing tickets between my business and clients.

The ease of configuration between Zendesk and Jira made the application a breeze to set up. The Customer Service Staff new the product and gave me answers almost immediately.

I understand that they are trying to build their Q&A section and forums, but sometimes there is a time crunch and a quick answer from the team is better.

Test it out, if it isnt what your looking for...keep looking

We needed to get the customers problems to the Developers and IT teams. Jira is not a good customer service ticket system, but is the leading for IT and Devops. By linking the two platforms, we cut out duplication and missed communication by creating one ticket for both systems and updating both as we go.

The tool is very powerful and can do so much when you need several instances to communicate with each other. It is a great time saver.

As a non-developer I found it very difficult to get started, even with the documentation. Video tutorials help though.

Just keeping 2 instances in synch, one is for an external group without write permission.

I like that Exalate lets me report on Azure DevOps issues through the integration with JIRA. Their customer service is also fantastic. Ariel, Jose, and Daniel have all been very helpful.

There is nothing I dislike about Exalate!

We have several business problems we are solving with Exalate: reporting, issue synchronization between JIRA and DevOps, and allowing our line of business to create DevOps tickets in JIRA