MS Azure DevOps Connector
The Microsoft Azure DevOps Connector connects ASM to Azure DevOps using API methodology.
The Microsoft Azure DevOps Connector connects ASM to Azure DevOps using API methodology, enabling you to create work items in DevOps from Calls in your ASM System, and create calls in your ASM System from work items in DevOps. The Microsoft Azure DevOps Connector enables you to integrate with any type of work item across all DevOps projects.
You can use Azure DevOps to update calls in ASM, and calls in ASM to update work items in DevOps.
Installing the Microsoft Azure DevOps Connector
For information about installing the Microsoft Azure DevOps Connector, contact your Account Manager.
For information about versions and licensing, see the ASM Connector Matrix.
After installation, the Alemba.Connector.Azure.DevOps.dll file should exist on your server.
Connection parameters
Alemba Service Manager™ uses the following connection parameters:
Required permissions
You need the permission Integration Setup in the General Access Security Role, to configure and use the Microsoft Azure DevOps Connector.
Additional Considerations
To create calls in ASM from work items in Azure DevOps, the DevOps project must have Service Hooks configured for ASM.
Configuring Service Hooks for ASM
Navigate to the Project Settings in Azure DevOps, and select Service Hooks from the menu on the left.
Press the Add button in the toolbar. The New Service Hook Subscription window appears.
Select Web Hooks from the menu on the left, and then press the Next button.
Select a value for the field Trigger on this type of event. These values are supported for ASM:
Work item commented on
Work item created
Work item deleted
Work item restored
Work item updated
Complete the trigger configuration by selecting filters as needed, and then press the Next button.
In the URL field, enter the URL for ASM in this format:
https://
Server_Name
/System_Name
/alemba.api/api/v1/webhook/azuredevops(where
Server_Name
is the ASM server name, andSystem_Name
is the ASM system name)https://AlembaServer/Production/alemba.api/api/v1/webhook/azuredevops
The Basic authentication username field requires the Login ID of an analyst record in ASM that has an IPK Management Security Role with permissions to create and update calls.
Enter the corresponding password for that analyst record in the Basic authentication password field, and then select Finish.
For more information, visit the official Microsoft page Create a service hook with WebHooks under Azure DevOps / Marketplace & extensibility / Service hooks / How-to Guides
Configuring ASM for Azure DevOps Service Desk Actions
Configuration is comprised of these steps:
Configuring Service Hooks for ASM
Enabling Service Desk Actions
Creating an Integration Source
Configuring Service Desk Actions
Enabling Service Desk Actions
Select ≡ > Admin > Integration.
In the Explorer pane, under Integration, select Integration Platform Settings to view the window.
Under section heading Service Desk Actions, select the Enabled checkbox, then save the changes.
In the Explorer pane, under Integration, select Connectors.
On the Integration Connectors window, locate the Azure DevOps Connector, and ensure that the Service Desk and Visible checkboxes are selected.
Creating an Integration Source
In the Explorer pane, under Integration, select Sources to view the window.
Select the button on the toolbar. In the pop up window, select Azure DevOps Connector from the drop-down list.
In the Integration Source Details window, complete the details. Refer to Connection parameters for more information.
Select the Test Connection icon on the toolbar to test the connection.
Save the details.
Configuring Service Desk Actions
An Integration Source for Azure DevOps must exist and connect successfully in ASM.
In the Explorer pane, under Integration, select Service Desk Actions to view the window.
In the Filter by Source field, select the Integration Source you created for the connector.
All Azure DevOps projects and work item types are listed in the browse table. Select the one you want to work with and then select .
The Service Desk Action Type window appears.
Select the New button to add a new mapping. The Mapping window appears.
Select the Action tab and complete the details:
Select the Criteria tab to specify the criteria for creating or updating work items in DevOps.
Select the Fields - Outgoing tab to map fields to be updated in the DevOps work item created from the call that activated this mapping.
Select the Outgoing - Response tab to map fields to be updated in the call when it creates the work item in DevOps. This tab can be ignored if this service desk action performs an Update.
The DevOps field Work Item ID must be mapped (in the Action column) if this service desk action performs a Create.
Select the Fields - Incoming tab to map fields to be updated in the call created from the DevOps work item that activated this mapping:
6. Select the Attachment- Criteria tab to define conditions for sending call attachments from ASM to the work item in DevOps that was created from this mapping. Different criteria can be configured for the Update vs Create mappings.
There are no conditions for attachments on the DevOps work item, all attachments are sent to the call in ASM.