EOL NOTE: We are moving Exalate for HP QC/ALM into basic maintenance mode. This transition period will last until June 2024, after which support will be halted completely. For more information, please see https://exalate.com/blog/end-of-support-hp/.
You can synchronize custom fields between HP QC/ALM and JIRA Instances.
In HP QC/ALM custom fields are called user fields. You should use the Physical name of the user field in the sync rules.
To get the physical name of a field in HP ALM use this URL:
|Available types of user fields in HP QC/ALM defect||Available types of custom fields in HP QC/ALM test cases|
There are always two main configuration points: a source side that sends data and a destination side that receives data.
The sending side needs to add the custom field to the replica in the Outgoing sync.
Defect custom field
Test case custom field
Add the code to the Outgoing sync to send the issue custom field value to the HP QC/ALM Instance.
Note : You must use the correct custom field name to get the defect/testCase custom field value.
For simple field types like text custom field, you can just assign the value of the received custom field to the local one.
The replica.customFields is set by the remote Instance. The issue.customFields is the custom field in Jira.
This is an example of how to assign the value of the received HP QC/ALM custom field to the local JIRA custom field.
Multi-select custom field type
Set the values received from the HP QC/ALM multi-select custom field to the Jira multi-select custom field options.
The replica.customFields is set by the Jira Instance. The defect.customFields and testCase.CustomFields are the custom fields in HP QC/ALM defects and test cases.
This is an example of how to assign the value of the received Jira custom field to the local HP QC/ALM custom field.