You can synchronize GitHub issues and pull requests with other work management systems, supported by Exalate.
Exalate has a distributed architecture. Exalate for GitHub converts issue tracker data to a common issue format and the other way around.
Exalate can be installed on Github Cloud and GitHub Enterprise Cloud.
You can exchange the following issue data between GitHub and any other trackers supported by Exalate.
Exalate for GitHub does not support attachment synchronization at the moment.
Check out this example on how to synchronize pull requests on GitHub with Jira.
Configuring Exalate for GitHub
Exalate for GitHub is hosted on our server.
For more details about information security—check out our Security And Architecture White-paper.
To start working with Exalate:
1. Install Exalate.
You can install Exalate for GitHub directly from the GitHub marketplace. The app is hosted on our server.
During your first installation, you need to complete a verification procedure. After completing you get:
- A verified Exalate instance.
- An active trial license.
- An admin account where you will receive error notifications.
Check out Install Exalate for GitHub for more information.
2. Set up a Connection.
Exalate can sync data after a connection between two instances is established.
To set up a connection, one side needs to configure the connection and send an invitation to the partner (the Destination instance).
The other side, depending on their Exalate version, needs to finish the configuration from their side.
For more details, check out Set up a connection in Exalate for GitHub.
3. Synchronize issues.
To start the issue synchronization for GitHub, you need to configure a trigger. It helps to synchronize issues according to the specified search query.
Configure the synchronization behavior of your use case with the help of these configuration guides.