Bitbucket Issue to Dataverse Project Sync

Overview

This solution keeps Bitbucket issues and a Dataverse mirror table in sync both ways, so project managers and stakeholders can track engineering work from Power Platform apps while developers stay in Bitbucket.

- Inbound (Bitbucket → Dataverse): when an issue is created or updated, the flow upserts a mirror row, maps the Bitbucket state to a Dataverse state label, and notifies the team in Teams. - Outbound (Dataverse → Bitbucket): when the mirror row's state changes in a Power App, the flow writes the new state back to the Bitbucket issue.

A source-flag loop guard (plus a trigger column filter) prevents the two directions from echoing each other into an infinite loop. A shared correlation id is stamped on every row for cross-system tracing.

> Built API-first (Dataverse workflow-table clientdata). All three flows ship Off and pass Flow Checker 0 errors / 0 warnings. Going live requires only connection authorization + environment-variable values (no logic changes).

Use Case

A team wants Bitbucket issues visible and updatable from Power Platform apps and dashboards, with status kept consistent on both sides. Devs continue triaging in Bitbucket; PMs adjust status in a model-driven/canvas app over the Dataverse table, and both views stay authoritative.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Bitbucket	shared_bitbucket	CreateHookIssueCreated CreateHookIssueUpdated
Microsoft Dataverse	shared_commondataserviceforapps	SubscribeWebhookTrigger ListRecords CreateRecord UpdateRecord
Microsoft Teams	shared_teams	PostMessageToConversation

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.

Comments sync

Add a CreateIssueComment (or Bitbucket REST POST .../issues/{id}/comments) on the Dataverse side and a comment trigger inbound to mirror discussion both ways.

Field mapping

Extend the table and the item field map to carry components, labels, milestones, or kind.

Bulk backfill

Add a one-time Recurrence flow that pages existing issues via Bitbucket REST and seeds the mirror table.

State map

Edit flowlibs_BitbucketStateMap / …Reverse to match your Dataverse choice labels (no logic change).

Assignee DM

Swap the channel post for a per-assignee Teams chat or an Outlook 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.

@{string(triggerBody()?['issue']?['id'])}

@{coalesce(json(parameters('EnvVar_BitbucketStateMap'))?[toLower(coalesce(triggerBody()?['issue']?['state'],'new'))], 'New')}

@greater(length(body('List_Existing_Rows')?['value']), 0)

@not(equals(triggerOutputs()?['body/flowlibs_source'],'Bitbucket'))

@{concat(parameters('EnvVar_BitbucketApiBaseUrl'),'/repositories/',parameters('EnvVar_BitbucketWorkspace'),'/',parameters('EnvVar_BitbucketRepoSlug'),'/issues/',triggerOutputs()?['body/flowlibs_issueid'])}

Customize & download