Installing And Configuring The Azure DevOps

The Azure DevOps integration helps the support team and product engineers to work together and know the up-to-date status of work items.

Checkout this video tutorial.

Key Features:

1. Create a link between existing work items and tickets.
2. Sync work items such as comments, status, and priority with tickets.
3. View Azure DevOps work item details such as title, work item type, and status on the ticket page.

Configure OAuth in Azure DevOps

1. Log in to Azure DevOps using an admin account.

2. Go to the organization where you want to integrate with BoldDesk.

3. Go to Organization Settings, then select Policies under Security.

4. Enable the Third-party application access via OAuth.

   

Install and configure the Azure DevOps

To install the Azure DevOps app, follow the given steps:

1. Click Admin menu > Marketplace.

2. Search and select Azure DevOps.

3. Click Install.

4. Choose an Organization from the list and map their Projects.

   

5. Select the Actions to be executed when a BoldDesk event occurs or vice versa.

   

6. In the Permission tab, under the App Permission window, select the roles for those who can access this Azure DevOps feature and click Save.

   

Configure sync actions

You can control the syncing of data between Azure DevOps and BoldDesk by selecting actions.

Comments sync

When you add a private note or update the status/priority of a ticket, you can select an action to add a comment to Azure DevOps Work Item and vice versa.

Configuring Azure DevOps mapping

Mapping organization and projects

The data from the selected projects can only be linked and synchronized data with tickets.

FAQ

Receiving the error “Work item not linked due to an invalid webhook”?

1. Please ensure that the Third-party application access via OAuth is activated for all organizations that you want to integrate with BoldDesk.
2. The user needs to possess admin permissions to create webhooks in Azure DevOps. Ensure that the user has Project Administrators permissions. If this is not the case, update the permissions and attempt the process again.