Start integrating with ONEiO for free!

Endpoint Configuration Guide - Azure DevOps

In this document, you can find the description of fields and additional instructions on making the endpoint in ONEiO ready for integration with your Azure DevOps instance. This endpoint is meant as a self-service and currently supports the Bugs, Epics, Issues, and Tasks as entity types. If anything is unclear or you get stuck with something that is not covered please reach out to us at




Status Sets the status of the endpoint. 
Name Name of the endpoint. It is recommended to use short names since this name is used in displays throughout ONEiO.
Base URL The base address of your Azure DevOps instance.



  [Your Azure DevOps] -> ONEiO
ONEiO Receiver QA/ONEiO Receiver PROD The address to insert to Azure DevOps Service Hooks. The targets are different depending on the ONEiO environment. See the Azure DevOps integration guide for more details.
Username Username to be used in Service Hooks in Azure DevOps for Basic Authentication.
Password Password to be used in Service Hooks in Azure DevOps for Basic Authentication.
Inbound Whitelist Filter

A comma-separated list of conditions must all match in order to allow the inbound message to be processed. Each contains an attribute name, operation, and value. Supported operation types are:

  • = (or ==) for EQUALS
  • != for NOT EQUALS
  • IN which evaluates to true if any of the values in the list are equal to the value compared to

The default value

resource.fields.System.ChangedBy!=${config:property.username} <${}>,resource.revision.fields.System.ChangedBy!=${config:property.username} <${}>

serves the purpose of filtering the echoing of integration messaging generated by ONEiO.




  ONEiO -> [Your MS Azure DevOps]
Token Name The name of the token created for the integration. See the integration guide for more detail.
Personal Access Token The value of the token.
Username The username of the user utilized by the integration. This will be required for the echo suppression mechanism defined in the Inbound Whitelist Filter property.
User Email The email associated with the user.


Entity types

To integrate with Azure DevOps, you can use defined entity types. These entity types are valid for Basic and Scrum boards. You can create more entity types to match the entities you are integrating with.

Currently supported entities:

  • Bug
  • Epic
  • Issue
  • Task
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request



Please sign in to leave a comment.