This documentation supports the 23.3 and consecutive patch versions of BMC Helix Multi-Cloud Broker.To view an earlier version, select the version from the Product version menu.

Reference of integration between Azure DevOps and BMC Helix ITSM incidents by using BMC Helix iPaaS

You can integrate BMC Helix ITSM with Microsoft Azure DevOps to synchronize BMC Helix ITSM incidents with Azure DevOps work items. When a work item is created in Azure DevOps, a corresponding BMC Helix ITSM is created, and the converse is true. This integration enables your service desk agents to collaborate with developers who use Azure DevOps.

BMC Helix Multi-Cloud Broker, along with BMC Helix iPaaS provides the Sync_BMC_Helix_ITSM_incident_and_Microsoft_Azure_DevOps_work_item.json integration template that you can use to integrate BMC Helix ITSM with Azure DevOps. You configure the integration in BMC Helix Multi-Cloud Broker and deploy the integration template to your BMC Helix iPaaS environment.

Related topic

Synchronizing-incidents-with-Azure-DevOps-work-items-via-BMC-Helix-iPaaS-powered-by-Jitterbit

List of project variables

The following sections describe the variables that you can update as per your requirements.

  • BMC Helix iPaaS project variables:

    Project variable

    Action

    BHIP_API_Name

    Enter the name for API that is created in BMC Helix iPaaS to receive BMC Helix Multi-Cloud Broker webhook requests.

    The default value of this variable is set to BMCHelixITSMIncidentAndAzureWorkItem.

    If required, you can change the name.

    BHIP_API_User_Roles

    Specify the organization roles that should have access to the new API. You can add multiple, comma separated values.
    Important: If you do not specify any value, all the organization roles get access to the new API.

    BHIP_MCB_API_Profile_User_Name

    Enter the user name that should be used while creating the BMC Helix Multi-Cloud Broker API profile.

    The integration template creates an API in BMC Helix iPaaS to handle requests from BMC Helix Multi-Cloud Broker.

    BHIP_MCB_API_Profile_User_Password

    Enter the password that should be used while creating the BMC Helix Multi-Cloud Broker API profile.

    The integration template creates an API in BMC Helix iPaaS to handle requests from BMC Helix Multi-Cloud Broker.

    BHIP_Vendor_API_Profile_Type

    The integration templates create APIs to accept requests from a vendor.

    Enter one of the following API authentication mechanisms that you want to use with this Azure DevOps API:

    • BASIC
    • ANONYMOUS
    • APIKEY

    The default value of this variable is BASIC.

    BHIP_Vendor_API_Profile_User_Name

    Enter the user name for the security profile that you want to use with the Azure DevOps API. 

    Important: Provide a value for this variable, only if you select the BASIC option in BHIP_Vendor_API_Profile_Type.

    BHIP_Vendor_API_Profile_User_Password

    Enter the password for the security profile that you want to use with the Azure DevOps API. 

    Important: Provide a value for this variable, only if you select the BASIC option in BHIP_Vendor_API_Profile_Type.

    BHIP_Vendor_API_Profile_ApiKey_Name

    Enter the APIKEY name for the security profile that you want to use with the Azure DevOps API. 

    Important: Provide a value for this variable, only if you select the APIKEY option in BHIP_Vendor_API_Profile_Type.

    BHIP_Host

    Enter the BMC Helix iPaaS instance URL where you want to run this project.

    Important: Make sure that you do not enter any leading and trailing spaces.

    BHIP_User_Name

    Enter the user name for the BMC Helix iPaaS instance.

    BHIP_User_Password

    Enter the password for the BMC Helix iPaaS instance.

    Enable_BMC_Helix_To_Vendor_Integration

    Enable the creation of Azure DevOps work items from BMC Helix ITSM incidents and synchronization of updates and comment.

    By default, this variable is set to true. If you want to disable the creation of Azure DevOps work items from BMC Helix ITSM incidents and synchronization of updates and comment, set the default value to false.

    Enable_Vendor_To_BMC_Helix_Integration

    Enable the creation of BMC Helix ITSM incidents from Azure DevOps work items and synchronization of updates and comment.

    By default, this variable is set to true. If you want to disable the creation of BMC Helix ITSM incidents from Azure DevOps work items and synchronization of updates and comment, set the default value to false.

  • Azure DevOps variables:

    Project variable

    Action

    AzureDevOps_Host

    Enter https:\dev.azure.com.

    Important: Make sure that you do not enter any leading and trailing spaces.

    AzureDevOps_Organization

    Enter your organization name in Azure DevOps.

    AzureDevOps_Personal_Access_Token

    Enter the Azure DevOps personal access token that you created earlier.

    AzureDevOps_Project

    Enter the project name that you want to use in Azure DevOps.

    (Optional) AzureDevOps_Webhook_Area_Path

    Enter the area path name based on which the Azure DevOps webhook can filter the work items.

    (Optional) AzureDevOps_Webhook_Tag

    Enter the tag name based on which the Azure DevOps webhook can filter the work items.

    AzureDevOps_Webhook_Work_Item_Type

    Enter the type of work item based on which the Azure DevOps webhook events should be filtered. The integration template supports the following work item types:

    • Bug
    • Epic
    • Feature
    • User Story

  • BMC Helix Multi-Cloud Broker project variables:

    Project variable

    Action

    MCB_Host

    Enter the BMC Helix Multi-Cloud Broker host URL to which the Azure DevOps work items should be synchronized.

    Important: Make sure that you do not enter any leading and trailing spaces.

    MCB_User_Name

    Enter the user name that enables users to interact with BMC Helix Multi-Cloud Broker.

    MCB_User_Password

    Enter the password for the provided user name.

    MCB_Vendor_Name

    This variable is auto populated. Do not change the default value.

    MCB_Assigned_Group

    Enter the name of the support group to which you want to assign the incident.

    MCB_Assigned_Support_Organization

    Enter the name of the support organization to which you want to assign the incident.

    MCB_Assigned_Support_Company

    Enter the name of the support company to which you want to assign the incident.

    MCB_Assigned_Company

    Enter the name of the company for which you want to create the incident.

    MCB_Assigned_Company_Id

    Enter the ID of the company for which you want to create the incident.

    MCB_Assigned_Business_Unit

    Enter the name of the business unit to which you want to assign the incident.

    The following variables are inputs from BMC Helix ITSM. Either enter values for these variables or map appropriate Azure DevOps fields if the data is available:

    Project variable

    Value

    ITSM_Company_Name

    Enter the company name for which the integration template needs to be run; for example, Apex Global.

    ITSM_Customer_First_Name

    Enter the first name of the BMC Helix ITSM customer.

    ITSM_Customer_Last_Name

    Enter the last name of the BMC Helix ITSM customer.

    ITSM_Incident_Type

    Enter any of the following incident types for which a corresponding Azure DevOps work item should be created:

    • User Service Restoration
    • User Service Request
    • Infrastructure Restoration
    • Infrastructure Event
    • Security Incident

    The default value of this variable is set to User Service Restoration.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*