Overview

Best of breed tools such as Azure DevOps Services (VSTS) and Micro Focus ALM bring richness to the enterprise ecosystem. The integration of Azure DevOps Services (VSTS) with Micro Focus ALM enhances collaboration between the development and quality assurance (QA) teams. This, in turn, helps deliver better quality products faster. There is no manual effort required from either of the teams to keep each other updated on the latest work status.

OpsHub Integration Manager integrates Azure DevOps Services (VSTS) and Micro Focus ALM bidirectionally. On this page, we will discuss the bi-directional integration of:

On this page, we will discuss the integration of:

Azure DevOps Services (VSTS) [Feature]
Azure DevOps Services
Micro Focus ALM [Micro Focus Quality Center Requirement]
Azure DevOps Services (VSTS) [Bug]
integration
Micro Focus ALM [ Micro Focus Quality Center Defect]

System Pre-requisites

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

Check out the pre-requisites for Azure DevOps Services (VSTS) and Micro Focus ALM systems before you proceed with the integration.

system prerequisites

Integration Configuration

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

OpsHub Integration Manager 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.

OpsHub Integration Manager

 

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

community

 

The integration configuration page opens.

  • Enter a unique name for the integration. For example, this integration is named Azure DevOps Services (VSTS) – Micro Focus ALM Integration.
  • Click Micro Focus ALM adjacent to the System 1 and System 2 fields one by one to configure Azure DevOps Services (VSTS) and Micro Focus ALM.

Micro Focus ALM

 


Configure System(s)

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


Micro Focus ALM

 

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.

Micro Focus ALM

 


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 Azure DevOps Services (VSTS) and Micro Focus ALM by clicking them. As we select Demo Project3 from Azure DevOps Services (VSTS) and Demo_SourceProject from Micro Focus ALM.

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

  • If you select Projects and Entities icon, the data would flow from Azure DevOps Services (VSTS) to Micro Focus ALM.
  • If you select Projects and Entities icon, the data flow would from Micro Focus ALM to Azure DevOps Services (VSTS) .
  • 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 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 Feature from Azure DevOps Services (VSTS) and Micro Focus Quality Center Requirement from Micro Focus ALM.

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: Feature and Requirement

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.


Mapping  projects

 

Mapping Mandatory Fields

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

Mapping Mandatory Fields The integration would fail if the mandatory fields are not mapped.

You will see, the API of Azure DevOps Services (VSTS) does not allow mandatory field to be called, but the API of Micro Focus ALM for this instance has Name and Requirement Type as mandatory field. We map them with Title and None of Azure DevOps Services (VSTS) respectively.

Mapping Mandatory Fields Mandatory fields might vary from one instance to another.

Mapping Mandatory Fields

 

Mapping Look-up Type Fields
Once you have mapped the Mandatory fields, you can now add more fields for mapping. We map the Look-up type fields first.: Look-up type fields are multi-valued fields. During mapping the fields for integration, the values of Look-up fields must be mapped for the mapped entities. In this case, we choose Status and Priority as the Look-up type fields to be mapped. We map:

  1. Priority to Priority
  2. Status to Status

The Look-up type fields are marked with alm location icon . Once you have mapped these fields in Azure DevOps Services (VSTS) and Micro Focus ALM, click alm location icon to map their values one by one.


Azure DevOps Services

 

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

For example, map the following values for Priority:

  • 1 – 1 – Low
  • 2 – 2 – Medium
  • 3 – 3 – High
  • 4 – 4 – Very High

You can map values for Status fields accordingly.

Now, save the 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 target field 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.


target 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 have mapped Description from Azure DevOps Services (VSTS) to Description in Micro Focus ALM.

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.


Bug and Defect

 

Entity: Bug and Defect

From Select Entities to Sync, select the relevant entities for both systems. In this case, we will select Bug from Azure DevOps Services (VSTS) and Defect from Micro Focus ALM. Create a Mapping for these entities as well.

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


Mapping Rich Text Fields

 

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

It is time to save this mapping now. Once the mapping is created, 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 
 entities

 


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 the 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 Azure DevOps Services (VSTS) would be the source system and backward direction would mean Micro Focus ALM would be the source system.

Criteria Filter 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.
Criteria Filter

If you want to specify conditions for synchronizing an entity between Azure DevOps Services (VSTS) and Micro Focus ALM to be integrated, use the Criteria Configuration feature.
For example, we only want to synchronize fields with Low Priority Bug to Azure DevOps Services (VSTS) then we set the configuration as shown here.

  • Click the mapping Criteria 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.
Criteria Configuration The query is different for different systems. You can refer to more details about Criteria Configuration in Azure DevOps Services (VSTS) and Micro Focus ALM from their respective configuration pages

  • From the Select criteria storage type drop-down list, select In Database option.

 


Criteria Configuration

 


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.


Criteria Configuration

 

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.

Criteria Configuration

 


Test the Integration

At this stage, test the integration by trying to synchronize data between the specified Azure DevOps Services (VSTS) and Micro Focus ALM projects.

Micro Focus ALM 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 a minute for the data to synchronize. If you face any issue, please refer this page for possible reasons and their fix.

Micro Focus ALM projects

Additional Configurations

Mapping User Fields

Choose the mapping in which you want to make the additional configuration. We choose Azure DevOps Services (VSTS) [Bug] – Micro Focus ALM [Micro Focus Quality Center Defect] mapping. Edit this map to add the changes.

We will add user-types of fields such as Author, Updated By, etc. in the mapping. The user fields vary from one system to another. For example, in this integration, we map the user fields: Assigned to in Azure DevOps Services (VSTS) to Assigned to in Micro Focus ALM. You are free to choose other fields.

Micro Focus ALM 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 projects

 

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