GitHub Issue to Planner Task Sync

Overview

GitHub Issue to Planner Task Sync automatically creates a Microsoft Planner task whenever a GitHub issue is assigned to you. The task includes the issue number, title, labels, assignee, and a direct link back to the GitHub issue — bridging developer issue tracking with project management in Planner.

Use Case

Development teams and project managers who use GitHub for issue tracking but Planner for daily task management need a bridge between the two systems. This flow eliminates manual task creation by automatically syncing assigned GitHub issues into Planner, ensuring nothing falls through the cracks. The task description includes the full issue context — labels, assignee, body text, and a clickable link to the original issue.

The flow is ideal for teams that:

• Development teams using GitHub for issue tracking and Planner for daily task management
• Project managers who need GitHub-assigned issues to surface automatically in Planner
• Teams that want issue context (labels, assignee, body, link) carried into Planner tasks
• Workflows where nothing assigned in GitHub should fall through the cracks

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.

Set environment variable values

Update all four env vars with your actual Planner Group ID, Plan ID, GitHub repo owner, and repo name.

Turn on the flow

Change the flow state from Stopped to On after import.

Update connections

If importing to a new tenant, create new GitHub and Planner connections and update the connection references.

Customize task title format

Edit the "Compose Task Title" action to change the [#number] title pattern.

Add bucket mapping

To map GitHub labels to Planner buckets, add a Switch action after "Compose Issue Labels" that sets a bucketId variable based on label names, then pass it to body/bucketId in the Create Planner Task action.

Add assignee mapping

To auto-assign the Planner task, add an assignments parameter to CreateTask_V3 mapping the GitHub username to a Microsoft 365 user email.

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.

concat('[#', string(triggerBody()?['number']), '] ', triggerBody()?['title'])

if(equals(triggerBody()?['labels'], null), 'No Labels', join(triggerBody()?['labels'], ', '))

coalesce(triggerBody()?['assignee']?['login'], 'Unassigned')

coalesce(triggerBody()?['body'], 'No description provided.')