This document shows an example of what needs to be done on Azure DevOps to make it integration-ready with an endpoint in your ONEiO subscription.
For any help with the below please don't hesitate to reach out at firstname.lastname@example.org.
In order to send messages from Azure DevOps to ONEiO we need to create two Service Hooks with the Webhook set as the service. For triggers, we are going to use the "Work item created" and the "Work item updated events and any filters you would like to employ additionally. The settings for the action should specify:
- Basic authentication username
- Basic authentication password
which come from the ONEiO app. For reference please use the "[Your Azure DevOps] -> ONEiO" section of the endpoint configuration guide. The rest of the settings can be left unchanged as default.
It may come in handy to use the webhook "Test" function to verify the messages are reaching ONEiO before proceeding with event testing.
In order to send messages from ONEiO to Azure DevOps, the user dedicated to the integration needs to generate a Personal Access Token and the details inserted into the ONEiO app.
The token scope "Work Items" with "Read & write" should cover the entities supported by the integration.
Once created the name and the value of the token can be saved in the ONEiO app.