There are certain cases when you need to stop a defect synchronization at some point. Since the Exalate app for HP QC/ALM is installed on a separate server it does not have a built-in feature that helps to stop sync directly on a defect.
A typical use case is when you, for example, need to stop one specific project synchronization.
This article shows how to stop defect synchronization. Please follow the steps below to stop the synchronization:
Stop the Exalate server for HP QC/ALM
In order to do that you should execute the query on the physical server where the Exalate server is installed.
You should get a root access to the host and execute the query as a root user.
Uninstall the Exalate for HP QC from the host by running
Ensure that Exalate does not try to sync anything from Jira to HP QC/ALM
In order to do that disable the Connection from JIRA instance side: Jira - Administration - Exalate - Connections - edit Connection - toggle the "Active" box to change the status.
To dispose of the Exalate's sync panel for the issues, navigate to Support Tools and then clean up sync by Connection.
Remove the post-function to Unexalate the issue on JIRA Server
You can find the list of workflows which use Exalate's post functions by executing an SQL query to your Jira Database.To find which particular transition is using Exalate's post-functions conditions and validators:
- Export workflows into xml
Open the file in a text editor
- Find all occurrences of com.exalate
- Find the closest enclosing tag <action and you will find an id and a name of the transition which uses Exalate post-function is and
In this example the transition id=711 and transition name="Escalate"