The integration of Micro Focus ALM (Micro Focus ALM) with Jira enhances collaboration between the customer service and development teams. This, in turn, helps resolve the customer issues faster and gives visibility to both teams into customer priorities.

On this page, we will discuss the integration of:

Micro Focus ALM Requirement

Micro Focus ALM Requirement
Jira Story


Micro Focus ALM Defect

Jira Bug


Integration Configuration

Log in into OpsHub Integration Manager. The default credentials are: User ID: admin, Password: Password.
OpsHub Integration Manager

Click Integrate on the top right corner of the screen and then click the Integrate icon . You will be prompted to enter the Integration Name and name of systems you want to integrate.

Enter a unique name for the integration. For example, this integration is named Micro Focus ALM – Jira Integration.

Click Micro Focus ALM – Jira Integration. adjacent to the System 1 and System 2 fields one by one to configure Micro Focus ALM and Jira.

Note: Please note, ‘systems’ here refer to Micro Focus ALM and Jira.

System Pre-requisites

Configuring system pre-requisites is mandatory for successful system configuration.

Check out the pre-requisites for Micro Focus ALM and Jira systems before you proceed with the integration.

Configure System (s)
Note: Before you proceed with the configuration, check whether the system is behind a proxy server, then set up proxy parameters in OpsHub Integration Manager.

Once you have fulfilled all the pre-requisites and are done with the above-mentioned check, configure Jira and Micro Focus ALM by following the steps given on Jira and Micro Focus ALM pages respectively.

configure Jira and Micro Focus ALM
configure Jira and Micro Focus ALM

After you save the respective configuration form after completion of the system configuration, the system automatically will be added to the integration form. You can now proceed to adding projects and entities in the integration.

configure Jira and Micro Focus ALM
Select Projects and Entities
Note: If the system is on HTTPS, then import SSL certificate onto OpsHub Integration Manager’s Java KeyStore before you proceed.
In the Add Project(s) to Sync section, select the projects you want to synchronize between Jira and Azure DevOps Server (TFS) by clicking them. For example, here we select Demo_SourceProject from Micro Focus ALM and Test Project from Jira.
Test Project

Once the projects are selected, define the source project and target project. If you select Test Project icon, the data would flow from Micro Focus ALM to Jira. If you select Test Project icon, the data flow would from Jira to Micro Focus ALM. If you want a bi-directional flow of data, select Test Project icon. Once the direction is selected, the arrows would turn grey. We have selected the bi-directional flow.
Test Project

The next step is to define entities that needs to be integrated and then the fields that need to be integrated for every entity mapped.
entity mapped

OpsHub Integration Manager fetches entities available in both systems and shows them in entities list for both systems. From the Select Entities to Sync section, select the relevant entities for both systems. In this case, we will select ‘Requirement’ from Micro Focus ALM and ‘Story’ from Jira.
OpsHub Integration Manager

Now, click OpsHub Integration Manager adjacent to Select fields to be Synced to create the mapping between these two entities. You will, now, be navigated to Mapping Configuration screen.

Mapping Fields
Requirement and Story Mapping
Following details are automatically populated in the Mapping section: Systems, Projects, and Entities, and Mapping Name. If you wish, change the name for the mapping in the Name field.
Mapping section

Now, either click the Create from Scratch button to define the mapping from scratch or click Auto Map button to automatically map all fields with same name. Even if you select the Auto Map button, OpsHub Integration Manager will allow you to remove or add more fields before saving mapping. We select Create from Scratch.
Mapping section

Now from the drop-down shown in the image below, select the Mandatory fields option. Choose Mandatory field(s) for Micro Focus ALM first and map them to the equivalent field Jira and then repeat the same steps for Jira. The integration would fail if the mandatory fields are not mapped.
Micro Focus ALM

The Mandatory field(s) for Micro Focus ALM are: Name and Requirement Type. Map them to Summary and OH_Default (select the option provided in drop-down list) fields in Jira respectively. The Mandatory field for Jira is Summary.

Note: Mandatory fields might vary from one instance to another.

Mandatory field

Mapping common fields
Once you have mapped the mandatory fields, you can now add more fields for mapping. We map:

  1. Status to Status
  2. Priority to Priority
Priority to Priority

Status and Priority are look-up type fields. The look-up type fields are marked with Priority to Priority icon . Once you have mapped these fields in Micro Focus ALM and Jira, click Priority to Priority icon to map their values.

Note: Values for look-up type fields may vary from one instance to another. Kindly map the values that you think are equivalent. You have to map the values for all look-up types fields before you proceed.

alues for look-up type fields
alues for look-up type fields

Save the value mapping.

It is time to save this mapping now. Click the Create Mapping button to create & save the mapping.

Once you save the mapping successfully, you will be further re-directed to the Integration page.
mapping successfully

Defect and Bug Mapping
From the Select Entities to Sync section, select the relevant entities for both systems. In this case, we will select ‘Defect’ from Micro Focus ALM and ‘Bug’ from Jira.
Micro Focus ALM

Create a Mapping for these entities as well. The image below shows a reference mapping for these entities.
Micro Focus ALM

You can refer to the previous mapping and follow the same steps further.

It is time to save this mapping now. Click the Create Mapping button to create & save this mapping as well.

Once you save the mapping successfully, you will be further re-directed to the Integration page.
Micro Focus ALM

Configure Filter(s) (Optional)

Criteria Filter/Configuration helps in integration of subset of entities based on some conditions. For example, user can specify that only bugs with high priority are to be synchronized or tickets that are closed should be synchronized. Even after the entities are integrated, this synchronization based on defined criteria is retained. Criteria Configuration can be applied in both the directions, forward direction would mean Micro Focus ALM would be the source system and backward direction would mean Jira would be the source system.

It is not a mandatory step for integration and if no filter needs to be applied on the entities to be synchronized, this step can be skipped.

But if you want to specify conditions for synchronizing an entity between Micro Focus ALM and Jira to be integrated, use the Criteria Configuration feature.

For example, we only want to synchronize fields with Low Priority Defect to Jira then we set the configuration as shown below.

You can refer to more details about Criteria Configuration in Micro Focus ALM and Jira from their respective configuration pages.

configuration pages
Save and Activate Integration
To save the integration in active mode, slide the Activate Integration button to the right.
configuration pages

As the final step, click Save button to save the integration.
configuration pages

The integration will be created. You will also get a pop-up at the bottom of the screen confirming the integration has been successfully configured and the integration will be listed in the integrations list.


At this stage, test the integration by trying to synchronize data between the specified Micro Focus ALM and Jira projects. Please note, you should not be using the integration user credentials to create entities in the systems as in this case the integration will not work.


Now, before you proceed further, please check the integration in action. Create/Update event in the source system and check whether the event synchronizes to the target system. If you face any issue, please refer to the Troubleshooting steps.

Additional Configurations
Mapping more fields: Now that you have set the basic integration in place, you can edit the integration to add more fields, for example user-types of fields such as Author, Updated By, etc. (the user field varies from one system to another). User fields are mapped by email id – search and set it. It will map the users based on email – if the email are same – Or if not same change, update to one to one XSL for user update. But before that you will have to de-activate and then edit the integration.


Choose the mapping in which you want to make changes. We choose Micro Focus ALM [Micro Focus Quality Center Defect] – Jira [Bug] mapping. Edit this map to add the changes. We map the user fields: ‘Assigned To’ in Micro Focus ALM to ‘Assignee’ in Jira. You are free to choose other fields.

Note: User fields are mapped by email id. If e-mail ids of the users are same in both the systems, it will be mapped automatically, but the email ids are not same, you will have to update the one-to-one XSL for user fields mapping.
Micro Focus ALM

At this stage, you can also map entities such as comments, attachments, and relationships.
map entities

Refer to the videos on this page to learn in detail about Comments and Attachments mapping.

For relationship mapping, toggle the Relationships button to the right.

map entities
In the Entity type section, map Requirements and Story.
map entities

Then click Next and go to the Link Type section and define that the Defect links coming from Micro Focus ALM block the Story in Jira.
Micro Focus ALM

Now, save the changes and click Update Mapping button.
Micro Focus ALM

Once you get a notification that mapping has been successfully updated, activate the integration and save it again.