Overview

Best-of-breed systems such as Micro Focus ALM/QC and Jira bring rich functionalities to the ecosystem.The integration of Jira with Micro Focus ALM makes it easier for the development, and quality assurance (QA) teams to collaborate with each other.This, in turn, helps in delivering a high quality product to customers at a faster pace. With this integration, there is no manual effort required to keep the teams updated on the latest work status.

OpsHub Integration Manager integrates Micro Focus ALM and Jira bi-directionally. On this page, we will discuss the bi-directional integration of:

Micro Focus ALM [Requirement]
Micro Focus ALM
Jira [Story]
Micro Focus ALM [Defect]
Micro Focus ALM
Jira [Bug]

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.

Micro Focus ALM

Integration Configuration

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

Integration Configuration Before you proceed with the configuration, check whether the system is behind a proxy server. If yes, then set up proxy parameters in OpsHub Integration Manager.

Integration Configuration

 

Click Integrate on the top right corner of the screen and then click the Integration Configuration icon .

Integration Configuration

 

The integration configuration page opens.

  • 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.

Micro Focus ALM

 


Configure System(s)

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.


pre-requisites

 

When you save the respective system configuration pages after configuring the systems, the systems will automatically be added to the integration. Proceed to adding projects and entities in the integration.

pre-requisites

 


Select Projects and Entities

Projects and Entities If you receive the following error: PKIX certification path not found and the projects and entities don’t load properly, 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.

Once the projects are selected, define the source project and target project.

  • If you select Projects and Entities icon, the data would flow from Micro Focus ALM to Jira.
  • If you select Projects and Entities icon, the data flow would from Jira to Micro Focus ALM.
  • If you want a bi-directional flow of data, select Projects and Entities icon.

Once the direction is selected, the arrows would turn grey. We have selected the bi-directional flow.


Projects and Entities

 

OpsHub Integration Manager fetches entities available in both systems and shows them in the 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.

The next step is to define the fields that need to be integrated for every entity mapped.So once the entities are selected,click the 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.


OpsHub Integration Manager

 


Mapping Fields

Entity: Requirement and Story

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.

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.


Systems, Projects, and Entities

 

Mapping Mandatory Fields

Now from the All fields drop-down list, select the Mandatory fields option.

Choose Mandatory field(s) for Micro Focus ALM first and map them to the equivalent field in Jira and then repeat the same steps for Jira.

Systems, Projects, and EntitiesThe integration would fail if the Mandatory fields are not mapped.

The Mandatory field(s) for Micro Focus ALM are: Name and Requirement Type. Map them to Summary and None (select the option provided in drop-down list) fields in Jira respectively. You might receive a message ‘About None’ when you map Requirement Type and None. Proceed with the mapping and select the value of the field from the drop-down list (as shown in the image).

Systems, Projects, and Entities

  • Mandatory fields might vary from one instance to another.
  • Jira does not allow accessing the Mandatory fields from the API, so check the Mandatory fields for Jira from Jira UI.

Systems, Projects, and Entities

 

Mapping Look-up Type 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

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


Micro Focus ALM and Jira

 

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.

For example, map the following values for Priority:

1 – Low – Low
2 – Medium – Medium
3 – High – High
4 – Very High – Highest
5 – Urgent – Critical

You can map values for Status fields accordingly.

Now, save the value mapping.


value mapping

 

Default Mapping is used to write default value to target field in case if there is no value coming from mapped source fields. Click Default Mapping to define the default mapping. The Default Mapping pop-up opens.


For user mapping, default value should be configured in form of user name or email as user name as expected by target end-point.


For user mapping, default value will not be written to target even if matching user not found in target. This will be done only if nothing coming from mapped source field.

Mapping Rich Text Fields

A rich-text field provides editing tools to customize the text entered in the field. We can map rich text fields with similar values from both the systems, for example, in this case we map Name from Micro Focus ALM to Summary in Jira.

Then click the Create Mapping button to save the mapping.

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

If you do not wish to add more entities, save the integration and activate it.


save the mapping

 

Entity: Defect and Bug

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.Create a Mapping for these entities as well.

Click the adjacentto Select fields to be Synced to create the mapping between these two entities. You will be navigated to Mapping Configuration screen.


save the mapping

 

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.

The image on right shows a reference mapping for these entities. Once you save the mapping successfully, you will be further re-directed to the Integration page.


mapping

 


Comments and Attachments Mapping

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

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


Configure Filter(s) (Optional)

Criteria Filter 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. Once the entity meets the criteria, it is always in synchronization, even after the criteria changes.

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.

mapping 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.
Configure Filter(s)

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 here.

  • Click the Configure Filter(s)icon against the mapping on which you are going to apply the criteria.
  • The Criteria Configuration pop-up opens. In the pop-up, select Yes from Configure Criteria list.
  • Enter the criteria query. Note, the query is different for different systems. You can refer to more details about Criteria Configuration in Micro Focus ALM and Jira from their respective configuration pages.
  • Select In Database from the Select criteria storage type drop-down list.

Configure Filter(s)

 


Save and Activate Integration

To save the integration in active mode, slide the Activate Integration button to the right.

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


Activate Integration

 

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.

Activate Integration

 


Test the Integration

At this stage, test the integration by trying to synchronize data between the specified Micro Focus ALM and Jira projects.

Micro Focus ALM and Jira projects You should not be using the integration user credentials to create entities in the systems as in this case the integration will not work.

Create/Update event in the source system and check whether the event synchronizes to the target system. Wait for one minute for the data to synchronize. If you face any issue, please refer this page for possible reasons and their fix.

Micro Focus ALM and Jira projects

Additional Configurations

Mapping User Fields

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 will add user-type fields such as Author, Updated By, etc. in the mapping. The user fields vary from one system to another.

We map the user fields: Assigned To in Micro Focus ALM to Assignee in Jira. You are free to choose other fields.

Micro Focus ALM and Jira projects 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 if the email ids are not same, you will have to update the one-to-one XSL for user fields mapping.

Micro Focus ALM and Jira projects

 

Once the additional configurations are completed successfully, update the mapping, and activate the integration, and save it again.