ADO Work Item Priority Override Approval

Overview

FlowLibs - ADO Work Item Priority Override Approval is a scheduled Cloud Flow that monitors Azure DevOps for work items recently escalated to P1/Critical priority. For each detected escalation, it routes an Approvals request to the designated product owner. If approved, the flow adds a timestamped approval comment to the work item. If rejected, it reverts the priority to P2 and notifies stakeholders via Teams and Outlook.

Use Case

In fast-moving sprint teams, developers sometimes escalate work items to P1/Critical without proper justification. This flow ensures every critical priority change is reviewed and approved by the product owner, maintaining priority hygiene across the backlog. Rejected escalations are automatically reverted, reducing noise in triage meetings.

Flow Architecture

Environment Variables

Connectors & Connections

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Change approval type

Modify the approvalType parameter from Basic (first to respond) to BasicGroup (everyone must approve) for stricter governance.

Add approval timeout

Add a parallel branch with a Delay action and terminate if the approval isn't responded to within X days.

Change revert priority

Modify the PATCH body value from 2 (High) to 3 (Medium) or another priority level to control where rejected items land.

Add more notification channels

Duplicate the Teams action for additional channels, or add Slack / mobile push notifications alongside the Outlook email.

Filter by area path

Add AND [System.AreaPath] UNDER 'ProjectName\\TeamArea' to the WIQL query to scope the flow to specific teams.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

[System.ChangedDate] >= @Today - 1

@body('Get_Work_Item_Details')?['fields']?['Microsoft.VSTS.Common.Priority']

@body('Start_Priority_Override_Approval')?['outcome']

@body('Start_Priority_Override_Approval')?['responses']?[0]?['responder']?['displayName']

@{concat('https://dev.azure.com/', variables('varAdoOrganization'), '/', variables('varAdoProject'), '/_workitems/edit/', items('For_Each_Work_Item')?['id'])}

@{utcNow('yyyy-MM-dd HH:mm:ss')}