Jira Customer-Facing Status Sync

Overview

This flow bridges internal Jira progress to customer communication. On a daily schedule it reconciles every active customer-linked Jira issue: it reads the live internal status from Jira, translates it into a sanitized customer-facing label via a configurable status map, and - only when the status has actually changed since the last sync - updates the customer's portal record in Dataverse and emails the customer a clean status update. No internal Jira detail (assignee, comments, raw status names) is ever exposed.

Why it matters: customers want progress visibility; internal Jira wording and detail are not appropriate to share. A mapped, sanitized status keeps customers informed safely, and change detection means they are only emailed when something genuinely moves.

Ships Off (Stopped).

Use Case

A delivery/support team tracks customer-driven work in Jira and maintains a Dataverse table linking each Jira issue to the customer who requested it. The team wants customers automatically kept up to date on progress without manually relaying status, and without leaking internal engineering detail.

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.

Schedule

Change the daily sync to hourly or business-hours only for faster customer updates.

Status map

Edit flowlibs_StatusSanitizationMap to match your Jira workflow's status names and preferred customer wording; unmapped statuses fall back to In Progress.

Notify selectively

Extend the change check to only email when the customer-facing label changes, not every internal hop.

Real-time variant

Swap the Recurrence for the Jira OnIssueUpdated trigger to react per-event.

Portal page

Surface the customer-facing status + last-synced on a Power Pages self-service status page.

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.

coalesce(body('Get_Jira_Issue')?['fields']?['status']?['name'],'Unknown')

coalesce(json(variables('varStatusMap'))?[outputs('Compose_Current_Internal_Status')],'In Progress')

not(equals(outputs('Compose_Current_Internal_Status'), items('Apply_to_each_Linked_Issue')?['flowlibs_internalstatus']))

concat(variables('varPortalUrlBase'), items('Apply_to_each_Linked_Issue')?['flowlibs_issuekey'])