Azure DevOps Bug Priority Change to Slack Alert
When a bug's priority is changed to Critical or Blocker, post an urgent alert to a Slack channel with the bug details.
Provided as-is, without warranty of any kind. Review and test each pattern in a non-production environment before deploying it to live automations. See our Terms.
Overview
This flow monitors an Azure DevOps project for work item updates and sends an instant Slack alert when a Bug's priority is escalated to Critical or High. It bridges the gap between Azure DevOps issue tracking and Slack team communication, ensuring high-priority bugs get immediate visibility without requiring team members to constantly monitor their ADO boards.
> Flow State: Stopped (demo) — Turn on after configuring environment variables and connections for your tenant.
Use Case
Scenario: A development team manages bugs in Azure DevOps but communicates day-to-day in Slack. When a QA engineer or product owner escalates a bug to Critical or High priority, the relevant Slack channel should be notified immediately so developers can triage without delay.
The flow is ideal for teams that:
- Developers — instant awareness of critical bugs without leaving Slack
- QA Engineers — confidence that escalated bugs get immediate attention
- Team Leads — visibility into priority changes across the project
Flow Architecture
When a Work Item Is Updated
Azure DevOps (polling, 5 min)Polls the configured ADO project for any work item updates. Uses `splitOn` to process each update individually.
Initialize Slack Channel Name
Initialize VariableLoads the target Slack channel from the `flowlibs_SlackChannelName` environment variable.
Initialize Priority Alert Thresholds
Initialize VariableLoads the configurable priority threshold string from the `flowlibs_BugPriorityAlertThresholds` environment variable.
Check If Bug With Alert Priority
If conditionTwo-part check: (a) Is the work item type "Bug"? (b) Does the bug's priority number appear in the threshold string? Both must be true.
- Compose Slack Alert Message — Builds a rich Slack message with bug ID, title, priority, state, assignee, changed-by, timestamp, description, and a direct link to the work item.
- Post Bug Priority Alert to Slack — Posts the composed alert message to the configured Slack channel.
Empty branch — no action.
Environment Variables
| Schema name | Type | Default | Description |
|---|---|---|---|
| flowlibs_AzureDevOpsOrgUrl | String | <configure> | The Azure DevOps organization account name (e.g., `contoso`). |
| flowlibs_AzureDevOpsProjectName | String | <configure> | The project to monitor for bug updates. |
| flowlibs_SlackChannelName | String | #general | The Slack channel to post alerts to. |
| flowlibs_BugPriorityAlertThresholds | String | 1 - Critical,2 - High | Comma-separated priority values that trigger alerts. ADO priorities: 1=Critical, 2=High, 3=Medium, 4=Low. |
Connectors & Connections
| Connector | API name | Actions used |
|---|---|---|
| Azure DevOps | shared_visualstudioteamservices | When a Work Item Is Updated (trigger) |
| Slack | shared_slack | Post Message |
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.
- Changing which priorities trigger alerts
- Update the flowlibs_BugPriorityAlertThresholds environment variable. The condition uses contains() to check if the bug's numeric priority appears in the threshold string. Examples: Alert on Critical only: 1 - Critical. Alert on Critical, High, and Medium: 1 - Critical,2 - High,3 - Medium.
- Changing the Slack channel
- Update the flowlibs_SlackChannelName environment variable to any channel your Slack connection has access to (e.g., #dev-alerts, #bug-triage).
- Monitoring a different ADO project
- Update flowlibs_AzureDevOpsOrgUrl with your organization account name and flowlibs_AzureDevOpsProjectName with the target project.
- Adjusting polling frequency
- Edit the trigger's recurrence settings. Default is every 5 minutes. Lower intervals give faster alerts but consume more API calls.
- Customizing the alert message
- Edit the Compose Slack Alert Message action. The message uses Slack markdown formatting (*bold*, \n for newlines). Available fields from the trigger body include all standard Azure DevOps work item fields.
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.
EXPR.01Work item type
Gets the work item type (Bug, Task, etc.).
EXPR.02Priority as string
Converts the numeric priority to string for threshold matching.
EXPR.03Priority threshold check
Checks if the priority appears in the configurable threshold list.
EXPR.04Null-safe assignee name
Null-safe access to the assigned user's display name.
EXPR.05Work item URL
Direct URL to the work item in Azure DevOps.
Comments
Sign in to join the conversation.
Sign inNo comments yet. Be the first to share your experience with this flow.