Bulk Sync: configuring mapping CSV

Originally asked by Brian Hyman on 01 May 2020 (original question)


How do I find the issue key pairs (in Github and Jira) when trying to configure a mapping CSV file for bulk sync in Exalate? Source: Github Cloud (old community)


Comments:

Juan Grases commented on 01 May 2020

Do both issues (Github and Jira) already exists? Were they mapped using exalate?

Brian Hyman commented on 01 May 2020

There are approximately 1000 issues in Github and 0 issues in Jira. I’m trying to get those 1000 Github issues into a specific Jira Project (of which there are two).

They have not yet been mapped by exalate. I’m trying to figure that out currently.

Brian Hyman commented on 01 May 2020

How can I learn or where can I access documentation on the platform search syntax to specify the filter query when setting up a trigger?

Juan Grases commented on 15 May 2020

Every platform has its own query language, for Jira, it is JQL:

https://www.atlassian.com/software/jira/guides/expand-jira/jql

For github, you can find more info here:

https://help.github.com/en/github/searching-for-information-on-github/understanding-the-search-syntax and https://developer.github.com/v3/search/

Answer by Juan Grases on 01 May 2020

I see, in that case, you will need to create a trigger on the Github side and bulk exalate, more details here:

https://docs.idalko.com/exalate/display/ED/Bulk+Exalate

and here:

https://docs.idalko.com/exalate/pages/viewpage.action?pageId=26084137