Bitbucket Pipeline Failure to Teams and Jira

Overview

This flow bridges Bitbucket Pipelines failures to triage and tracking. When a build changes state on a protected branch, Bitbucket posts a commit-status webhook to the flow. If the build failed, the flow opens (or updates) a Jira bug assigned to the author and posts a failure card to a Microsoft Teams dev channel; when the build recovers, it transitions the bug to Done and closes it. A Dataverse ledger keyed by repo|branch makes the whole thing idempotent, so a flapping build updates one bug instead of spawning duplicates.

Why it matters: Broken builds on main are urgent but easy to miss in email. Routing to Teams plus a tracked, auto-closing Jira bug ensures every failure is seen, owned, and resolved.

Status: Built — ships Off (demo). Going live requires only connection authorization, env-var configuration, and registering the Bitbucket webhook.

Use Case

A development team on Bitbucket Cloud wants CI failures on protected branches surfaced in Teams and tracked as Jira bugs automatically, with the bug closing itself once the build is green again.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Bitbucket	shared_bitbucket	ListPullRequests
Microsoft Teams	shared_teams	PostMessageToConversation
Jira	shared_jira	CreateIssue_V3 AddComment_V2 UpdateTransition
Microsoft Dataverse	shared_commondataserviceforapps

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.

Per-author assignment

Replace the single flowlibs_JiraAssigneeAccountId with a lookup (Dataverse table or env-var JSON map) from Bitbucket display name → Jira accountId so the bug routes to the real author.

Severity / on-call escalation

Escalate main-branch failures to an on-call group (e.g. Teams mention or PagerDuty) when Failure Count exceeds a threshold.

Auto-revert

On repeated failures, open a revert PR via the Bitbucket connector.

Flaky detection

Track intermittent failures by comparing consecutive states on the same commit and tag the bug.

Resolution status

Drive flowlibs_JiraDoneTransitionId and an optional resolution field from env vars to match your Jira workflow.

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.

@contains(split(toLower(parameters('EnvVar_ProtectedBranches')),','), toLower(variables('varBranch')))

@toLower(concat(repository/full_name, '|', commit_status/refname))

@greater(length(coalesce(outputs('Search_Existing_Bug')?['body/value'], json('[]'))), 0)

@and(equals(variables('varBuildState'),'SUCCESSFUL'), greater(length(...search...), 0))

@add(int(coalesce(first(...)?['flowlibs_failcount'],0)),1)

Customize & download