You can synchronize GitHub issues with Jira or other supported issue trackers.
Exalate has a distributed architecture. An Exalate app for GitHub is responsible for translating issue tracker based information to a common issue format (and the other way around).
The Exalate protocols are fully asynchronous, which implies that both ends must be able to initiate http(s) requests.
You can exchange the following issue data between the GitHub and Jira
- issue number ↔ issue key
- title ↔ summary
- comments ↔ comments
- issue body ↔ description
- user ↔ reporter
- state ↔ status
- assignees ↔ assignees
- labels ↔ labels
- milestones ↔ fix versions
- closed at ↔ resolution date
- created ↔ created at
Exalate app for GitHub does not support attachment synchronization at the moment.
Exalate architecture requires installing one Exalate application for each instance.
You can install Exalate for GitHub app directly on organizations and user accounts and grant access to specific repositories. The app is hosted on our server. More details.
Once the installation is finished you need to get the evaluation license.
Set up a Connection
Synchronization between two instances requires a configured Connection.
One side needs to initiate the connection and send an invitation to the partner (the Destination instance).
The other side needs to finish the configuration from their side.
You can synchronize with supported issue tracking platforms. For example, you can sync between Github and JIRA Cloud or JIRA Server, even if your JIRA server is not accessible from the outside network.
You need to define the GitHub repository to sync issues from. For more details check typical use cases.
To start synchronization with your partner - Initiate Connection.
If you have an Invitation code - Accept an Invitation.
Synchronize an issue
To start issue synchronization for GitHub you need to configure a trigger. It helps to synchronize issues according to the specified search query.