Sprint Rollover Automation

Overview

Every other Friday at 17:00 UTC this flow finds the next-due open GitHub milestone in the configured repo, treats it as the current sprint, closes it (state=closed, due_on=utcNow()), pulls every issue still open under that milestone, and emails a styled HTML rollover digest to the configured Project Manager distribution list. Designed for engineering teams that use GitHub milestones as sprint containers and want a zero-touch close every two weeks.

Use Case

Sprint hygiene rots when nobody owns the close ritual — milestones drift open, "carry-over" issues silently accumulate, and the PM finds out at standup that last sprint never officially ended. This flow takes the busywork out: every other Friday it closes the active milestone and hands the PM a clean, ranked list of what didn't ship, so the next-sprint conversation starts with data instead of guesswork.

The flow is ideal for teams that:

• Zero-touch biweekly milestone close — no PM clicks
• HTML digest of unfinished issues with title, assignee, and direct link
• Subject line surfaces the unfinished count for inbox triage
• All env-var driven — drop into any repo with three values
• Defensive coalesce on assignee?.login keeps unassigned issues in the table
• Flow Checker clean on ship (0/0)

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
GitHub	shared_github	GetMilestones (list open milestones, sorted by due date) UpdateMilestone (closes the current sprint milestone) GetIssues (pulls issues still open under the milestone)
Office 365 Outlook	shared_office365	SendEmailV2 (delivers the styled HTML rollover digest)

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 FlowLibsSprintRolloverAutomation solution, set flowlibs_GitHubOwner, flowlibs_GitHubRepository, and flowlibs_DigestRecipientEmail, bind the GitHub and Outlook connection references, adjust the recurrence timeZone if the PM team prefers local-time delivery, then turn the flow on.

Different cadence

Change the Recurrence frequency from 2 weeks to 1 or 3 weeks to match the team's sprint length.

Auto-create next milestone

When the GitHub connector ships CreateMilestone, slot it in after Close_Current_Sprint_Milestone to skip the human follow-up step.

Carry-over auto-reassignment

Add a Foreach over Get_Unfinished_Issues calling GitHub UpdateIssue to set milestone to the next milestone number.

Slack instead of email

Replace SendEmailV2 with the Slack PostMessage action and swap flowlibs_DigestRecipientEmail for a Slack channel ID env var.

Multi-repo digest

Replace the two GitHub env vars with a JSON array env var of {owner, repo} and Foreach over it, accumulating rows into a single email.

Velocity stats

Add a closed-issues GitHub call to compute completion rate vs. carry-over and surface it in the email header.

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.

@first(body('Get_Open_Milestones'))?['number']

@utcNow()

@concat('<tr><td>', string(item()?['number']), '</td><td>', item()?['title'], '</td><td>', coalesce(item()?['assignee']?['login'], '(unassigned)'), '</td><td><a href="', item()?['html_url'], '">link</a></td></tr>')

@{join(body('Select_Issue_Rows'),'')}

@length(body('Get_Unfinished_Issues'))

@formatDateTime(utcNow(),'yyyy-MM-dd HH:mm')

Customize & download