Azure DevOps · Arazzo Workflow

Azure DevOps Board Bug Acknowledgement

Version 1.0.0

Query a board column with WIQL, fetch the work item type, and acknowledge the top bug.

1 workflow 3 source APIs 1 provider
View Spec View on GitHub AgileCI/CDDevOpsProject ManagementVersion ControlArazzoWorkflows

Provider

microsoft-azure-devops

Workflows

board-bug-acknowledgement
Find the top board bug via WIQL and post an acknowledgement comment.
Runs a WIQL query, and when a bug is found, reads the Bug type definition and adds an acknowledgement comment to the matched work item.
3 steps inputs: accessToken, apiVersion, commentText, query outputs: bugWorkItemId, commentId, typeName
1
queryBoardColumn
Execute the WIQL query to find the top bug in the board column. The WIQL endpoint accepts a plain JSON body with a single query property.
2
getBugType
Read the Bug work item type definition to confirm the type and its valid states before commenting.
3
acknowledgeBug
Post an acknowledgement comment on the matched bug work item. This endpoint uses application/json (not the JSON Patch media type).

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Azure DevOps Board Bug Acknowledgement
  summary: Query a board column with WIQL, fetch the work item type, and acknowledge the top bug.
  description: >-
    Acknowledges the top bug sitting in a board column. Azure Boards are backed
    by work item tracking, so this flow adapts the requested "boards" theme to
    the Work Items specification: it runs a WIQL query (typically scoped to a
    board column via System.BoardColumn) to find the top bug, branches on whether
    anything matched, reads the Bug work item type definition to confirm the
    type's states, and posts an acknowledgement comment on the matched work item.
    The WIQL and comment endpoints use application/json. Every step spells out its
    request inline so the flow can be read and executed without opening the
    underlying OpenAPI description.
  version: 1.0.0
sourceDescriptions:
- name: commentsApi
  url: ../openapi/microsoft-azure-devops-comments-api-openapi.yml
  type: openapi
- name: workItemTrackingApi
  url: ../openapi/microsoft-azure-devops-work-item-tracking-api-openapi.yml
  type: openapi
- name: workItemTypesApi
  url: ../openapi/microsoft-azure-devops-work-item-types-api-openapi.yml
  type: openapi
workflows:
- workflowId: board-bug-acknowledgement
  summary: Find the top board bug via WIQL and post an acknowledgement comment.
  description: >-
    Runs a WIQL query, and when a bug is found, reads the Bug type definition and
    adds an acknowledgement comment to the matched work item.
  inputs:
    type: object
    required:
    - apiVersion
    - query
    - commentText
    properties:
      apiVersion:
        type: string
        description: Azure DevOps REST API version (e.g. 7.1).
      query:
        type: string
        description: WIQL query selecting bugs in a board column.
      commentText:
        type: string
        description: Acknowledgement comment to post on the matched bug.
      accessToken:
        type: string
        description: Azure DevOps bearer (OAuth 2.0) access token.
  steps:
  - stepId: queryBoardColumn
    description: >-
      Execute the WIQL query to find the top bug in the board column. The WIQL
      endpoint accepts a plain JSON body with a single query property.
    operationId: workItems_queryByWiql
    parameters:
    - name: api-version
      in: query
      value: $inputs.apiVersion
    requestBody:
      contentType: application/json
      payload:
        query: $inputs.query
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      topWorkItemId: $response.body#/workItems/0/id
    onSuccess:
    - name: hasBug
      type: goto
      stepId: getBugType
      criteria:
      - context: $response.body
        condition: $.workItems.length > 0
        type: jsonpath
    - name: noBug
      type: end
      criteria:
      - context: $response.body
        condition: $.workItems.length == 0
        type: jsonpath
  - stepId: getBugType
    description: >-
      Read the Bug work item type definition to confirm the type and its valid
      states before commenting.
    operationId: workItemTypes_get
    parameters:
    - name: api-version
      in: query
      value: $inputs.apiVersion
    - name: type
      in: path
      value: Bug
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      typeName: $response.body#/name
      referenceName: $response.body#/referenceName
  - stepId: acknowledgeBug
    description: >-
      Post an acknowledgement comment on the matched bug work item. This endpoint
      uses application/json (not the JSON Patch media type).
    operationId: workItems_addComment
    parameters:
    - name: api-version
      in: query
      value: $inputs.apiVersion
    - name: id
      in: path
      value: $steps.queryBoardColumn.outputs.topWorkItemId
    requestBody:
      contentType: application/json
      payload:
        text: $inputs.commentText
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      commentId: $response.body#/id
  outputs:
    bugWorkItemId: $steps.queryBoardColumn.outputs.topWorkItemId
    typeName: $steps.getBugType.outputs.typeName
    commentId: $steps.acknowledgeBug.outputs.commentId

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/microsoft-azure-devops-board-bug-comment-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.