You can synchronize with any of the supported issue tracking platforms
Exalate has a distributed architecture. An Exalate app for HP ALM/QC is responsible for translating issue tracker based information to a common issue format (and the way around).
Exalate app for HP QC/ALM supports HP QC/ALM v. 11.05 - 12.55
HP ALM/QC to Jira Server
HP ALM/QC to Jira Cloud
The exalate protocols are fully asynchronous, which implies that both ends must be able to initiate http(s) requests
To set up a synchronization, between HP ALM/QC and JIRA instance you need the following components:
|HP ALM/QC Instance||JIRA Instance|
|1||HP ALM Instance||JIRA Instance|
Exalate app for HP ALM/QC(installed on a separate Server)
|Exalate app for JIRA, installed on the JIRA instance|
|3||A network which allows unobstructed HTTP(S) based communication|
|4||Valid Exalate license.|
Check the HP ALM and Jira integration use case.
Exalate app for HP ALM/QC configuration steps overview
Install Exalate app for HP ALM/QC
Exalate architecture requires installing one Exalate application for each instance.
As far as HP ALM/QC does not offer any integration option for plugins, you need to install a separate server to store the Exalate for HP ALM/QC application and configure it to communicate with your HP ALM/QC. More details.
Configure the app to communicate with your HP ALM/QC
To establish the connection between the Exalate app for HP ALM/QC and the HP ALM instance configure the General Setting. More details. Exalate does not synchronize defects created by the Exalate proxy to avoid loops. Please, create a separate user for applying changes locally. The user should have administrative permissions to be able to see all the HP ALM/QC projects and user field configurations
Exalate does not synchronize defects created by the Exalate proxy to avoid loops. Please, create a separate user for applying changes locally.
The user should have administrative permissions to be able to see all the HP ALM/QC projects and user field configurations
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 different issue tracking systems by selecting offered Connection types. For example, you can sync between HP ALM/QCand JIRA Cloud or JIRA Server, even if your JIRA server is not accessible from the outside network. For more details check typical use cases.
Synchronize a defect
Find out ways to synchronize defects.
Configure the synchronization behavior of your use case with the help of configuration guides.