Round-Robin Issue Auto-Assign

Overview

This flow monitors GitHub for newly opened issues and auto-assigns them to team members in a round-robin rotation. When a new issue arrives, the flow reads a rotation pointer from a SharePoint list, selects the next developer in the assignee list, assigns the issue, and increments the pointer for balanced load distribution.

Use Case

Development teams need fair issue distribution without manual assignment. This flow automates round-robin assignment so every team member gets equal work, eliminates dropped issues, and maintains an auditable assignment history in SharePoint.

The flow is ideal for teams that:

• Automatic round-robin assignment — every developer gets equal issues
• Balanced load distribution via modulo arithmetic
• Rotation state persisted in SharePoint — survives flow restarts
• No duplicates — upsert logic ensures one record per issue
• Fully env-var-driven — no flow edits required for new assignee lists

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.

Deploying to Another Environment

Import the solution and create the SharePoint rotation list (columns: Title, LastAssignedIndex; seed row: Title=default, LastAssignedIndex=0). Update the five env vars with your target GitHub org, repo, SharePoint site, and list name. Open the flow in the designer and re-bind the SharePoint actions to clear Flow Checker dynamic-schema notices. Confirm connection references are bound to valid GitHub and SharePoint connections, then turn the flow on.

Multiple rotation tracks

Create additional SharePoint rows (e.g., Title=frontend, Title=backend) and branch the condition on repo name to use different rotation keys, allowing parallel rotations per team or component.

Weighted assignment

Replace the modulo math with a lookup that weights some developers higher (e.g., assign 2 issues to senior devs for every 1 to juniors), useful when capacity varies across the team.

Exclude specific developers

Filter the assignees array after GetAssignees to remove names from a blocklist (e.g., on-leave or focus-mode developers) before computing the rotation index.

Reassign stale issues

Add a scheduled flow that runs daily, queries issues assigned more than 7 days ago without activity, and reassigns them via this same round-robin logic to prevent stalls.

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.

if(equals(variables('varCount'), 0), 1, mod(add(variables('varLastIndex'), 1), variables('varCount')))

json(concat('{"assignee":"', variables('varSelectedAssignee'), '"}'))