francis Atlassian Partner

All of it is possible. The incoming and outgoing sync scripts are groovy based, and in that context, any type of functionality can be built - including the sync of insight objects itself. It just takes some what more work.

(I'm with the team that is building and selling Exalate) Also insight objects can be synced - check following example meant for Jira On Premise https://docs.idalko.com/exalate/display/ED/How+to+sync+Insight+custom+fields There is a nice discussion on the exalate community on syncing in the cloud.…

Hi @Peter Weimer (welcome to the community) I'm Francis - with the idalko team. What version of Jira are you using?

Hi Deepan, Francis here - PM for the table grid. We had once a customer who started to load 4000+ rows in a single table, and this did lead to problems. The question is - why would you need this type of setup. What is the use case

The regression validation is almost complete and you can expect an updated version on the marketplace.

Hi @Rob Horan , (I'm a colleague of Dhiren, and also with Exalate) We know that there is a learning curve here - and it is not easy for rooky users The details of the nodeHelper class is detailed https://docs.idalko.com/exalate/display/ED/nodeHelper Let us know how the documentation can be improved.

Hi @Rob Horan (I'm with the Exalate team) Exalate is indeed an integration solution and NOT a migration tool. Check the document Using Exalate for migration purposes for more details and caveats. Note however - In many cases a big bang approach is not possible due to organisational constraints. In this case, companies are…

Absolutely true, a tool will never stop to enter mitsakes - fully understood. Still - what I'm looking for is for the type of update - illustrated in the question - where 2 updates are crossing each other. Is there an add-on or a technique that would flag that there might be a problem? There is this…

Yes - there is an UnexalateEvent > scheduleUnexalateEvent(connection: IConnection, issueKey: IIssueKey)

There is something funky going on with one of the users. If you remove the col.iassignee from the configuration - will it still throwing?

Hello @Karen Shaheen (I'm product manager of Exalate) As detailed in the ticket @Trudy P Claspill mentioned - if you make the attachments public, your dev will be allowed to see these (without a zendesk account) If you think this is not secure, have a look at Exalate which allows to transport the attachments Check the…

Hi @erika , @Trudy P Claspill Exalate only provides integration capabilities with a couple issue trackers. Certainly not Conclusion ...

Hi @Ben Gallimore - is the internal jira on Jira Cloud, or on premise

The snippet has also an example of the code that can be inserted in the outgoing sync of the connection (so that it is not necessary to use a script listener)

Hi @siddhesh pawar Checkout this thread on the exalate community https://community.exalate.com/questions/25070212/converting-html-to-wiki---the-azure-devops-style It should provide you the necessary details. Francis

Hi @Madhu Reddy The exalate and unexalate operation can be built into workflow transitions using postfunctions. If you want to restrict access to these operations, create a transition and restrict it there with conditions. Tracking who performed a certain transition can then be added as part of these.

Hi @Jfmeza We have an extensive network of Exalate partners (130+) who know how to collect the requirements around the sync and make sure that it works. https://exalate.com/partners/ I'm sure you can find one that is meeting your expectations.

Yes - absolutely - this is a core use case and used at many different customers. The only difference is that this is continuous and not 'time to time' - but i guess that would be ok also

Thanks @Pramodh M for mentioning Exalate. @Khang Pham Configuration Manager is a good bet. There is a cost associated to it, but it is much less costly (timewise) than having to do it manually.

Hi both, The approach is, that whenever a new issue needs to be created, a message is sent from the receiving end (where the issue is being created) back to the sending end (where the issue is being exalated from) containing the id. Checkout…

Exalate will NOT synchronise configurations. The assumption is that the workflow is setup on both sides. Once that this is done - exalate can be used to synchronise ticket information bidirectionally - including the status information. With the configuration of the connection - you can specify how the status needs to be…

This is one of the use cases also covered by Exalate (I'm with the vendor of Exalate) With that solution, you can automatically escalate issues from a.atlassian.net to b.atlassian.net for all tickets that match certain criteria (or even all of them) Still there are a couple of challenges with syncing which needs some…

Hi @Rob Horan What document are you referring to? So - what type of comment sync do you need. * Direction * Create your own comments * Internal notes or customer visible comments

You can access this information when Exalate is deployed on premise. On exalate cloud - the only rest api available is the one to monitor the number of outstanding errors.

The panel is a representation of the data maintained by the app. There are a couple of rest api's accessible Check https://docs.idalko.com/exalate/display/ED/Using+REST+API+for+monitoring+purposes Hope this helps

:headscratch: I don't understand the use case - but I think you will be fine. Is your integration platform a commercial product?

Hi @Ola Carlander The exalate sync status is reported by a web panel and is not part of the issue. What is your use case? Francis ps - I'm part of the exalate team

(Francis here - with the Exalate team - another issue sync app) FYI We are continuing supporting our apps way beyond the EOL of the underlying application.. For instance - our apps are still supporting Jira 6.3. Although that Atlassian stopped to support this version long time ago, there are still customers actively using…

Following should work replica.summary = issue.summary?.substring(0,Math.min(issue.summary?.length(), 254)) You can confirm by adding (after that line) debug.error("Length of summary is ${replica.summary?.length()}")

Thanks @Tom Lister , much appreciated. Hi @Esther Strom We can demo the capabilities of Exalate - it is a cross-company integration solution covering next to Jira Cloud (and data center), also ServiceNow, Salesforce, Azure Devops, Zendesk and Github, and more integrations are coming up. There is a free plan for setting up…