Bitbucket Pull Request SLA and Review Load Balancer

Overview

This flow keeps Bitbucket code review fast and fair. On a schedule it lists open pull requests, finds those that have waited past a configurable review SLA without an approval, picks a reviewer by round-robin load balancing (skipping anyone out of office), nudges that reviewer in a Microsoft Teams channel, and escalates genuinely stale PRs to the team lead by Outlook email. Review latency and uneven reviewer load slow delivery and burn people out; automated SLA enforcement plus fair assignment keeps the queue moving and equitable, with zero hardcoded values so it ports to any tenant by editing environment variables only.

Use Case

A development team wants every open PR reviewed within an SLA window, reviewer workload spread evenly across an available pool, out-of-office reviewers skipped, and any PR that goes stale escalated to the lead so nothing silently rots in the review queue.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Bitbucket	shared_bitbucket	ListPullRequests
Microsoft Teams	shared_teams	PostMessageToConversation
Office 365 Outlook	shared_office365	SendEmailV2

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.

Cadence

Change the Recurrence frequency/interval to match working hours (e.g. hourly during 9-5).

SLA & escalation windows

Tune flowlibs_ReviewSlaHours and flowlibs_StaleEscalationHours.

Reviewer pool & OOO

Maintain flowlibs_ReviewerPool / flowlibs_OutOfOfficeReviewers (ideally fed from an HR/OOF source).

Smarter balancing

Replace round-robin with load-weighted selection (open reviews per person from a Dataverse table) or CODEOWNERS-based routing.

De-dupe nudges

Add a Dataverse ledger keyed by PR id so the same PR is not re-nudged every run.

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.

@div(sub(ticks(utcNow()), ticks(coalesce(item()?['created_on'], utcNow()))), 36000000000)

@if(greater(outputs('Compose_Eligible_Reviewer_Count'),0), trim(string(body('Build_Eligible_Reviewer_Pool')[mod(int(coalesce(item()?['id'],0)), outputs('Compose_Eligible_Reviewer_Count'))])), 'unassigned')

@and(greater(outputs('Compose_PR_Age_Hours'), variables('varReviewSlaHours')), equals(length(body('Filter_Approved_Reviewers')), 0))

Customize & download