Jira Issue SLA Breach Escalation

Overview

This flow enforces SLAs on Jira issues. On an hourly recurrence it runs a JQL search for issues that are open and past their SLA/due target, then for each breaching issue it adds an escalation comment, reassigns it to a first-tier escalation owner, and pings the team lead in a Teams channel. A Dataverse breach-ledger tracks how many times each issue has been escalated and the date it was last escalated; on a repeat breach (escalation count ≥ a configurable threshold) it raises the issue priority and emails the manager. The ledger also de-duplicates so an issue is escalated at most once per day.

Why it matters: Jira's native SLA features live in JSM premium tiers; many teams on standard Jira have no automated breach handling. This flow brings an SLA nudge-then-escalate ladder to any Jira project using JQL + comments + assignment, with management visibility and an auditable escalation history.

Status: Built as a demo — ships Off (Stopped). Going live requires only authorising the connections and setting the environment variable values.

Use Case

A delivery team commits to response/resolution times, but issues silently age past them. They want an automatic ladder so breaches get a human owner and management visibility without a daily manual triage meeting. First breach → comment + reassign + Teams ping. Repeat breach → priority bump + manager email. The Dataverse ledger prevents the same issue being re-escalated every hour and records the full escalation history for audit.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Jira	shared_jira	AddComment EditIssue
HHTTP	http	GET /rest/api/3/search/jql
Microsoft Teams	shared_teams	PostMessageToConversation
Office 365 Outlook	shared_office365	SendEmailV2
Microsoft Dataverse

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.

SLA source

Change flowlibs_SlaJqlFragment. If you store SLA targets in a custom field, fold it into the JQL via cf[12345].

Escalation matrix

The demo reassigns every breach to a single flowlibs_EscalationAssignee. Replace it with a Dataverse/SharePoint lookup keyed by component or priority for a true matrix.

Repeat threshold / priority

Adjust varRepeatThreshold (Initialize Variable) to escalate to management sooner, and varBumpPriority to match your project's priority scheme (e.g. Highest).

De-dup window

The flow escalates an issue at most once per calendar day (UTC). To change the cadence, edit Compose Last Day / Compose Today (e.g. compare full timestamps with an hours threshold).

Recurrence

The trigger runs hourly in Eastern Standard Time; change the frequency/time zone to fit your working hours.

Going live

Authorise the Jira, Teams, Outlook and Dataverse connections, set all flowlibs_ env var values (especially flowlibs_JiraApiToken), and turn the flow On.

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('project = ', variables('varProjectKey'), ' AND ', variables('varSlaJql'), ' ORDER BY priority DESC')

@{concat(variables('varJiraBaseUrl'), '/rest/api/3/search/jql?maxResults=50&fields=summary,status,priority,assignee,duedate&jql=', encodeUriComponent(outputs('Compose_Full_JQL')))}

@concat('flowlibs_name eq ''', items('Apply_To_Each_Issue')?['key'], '''')

@if(empty(outputs('Compose_Ledger_Row')), 0, int(coalesce(outputs('Compose_Ledger_Row')?['flowlibs_escalationcount'], 0)))

@or(equals(outputs('Compose_Prior_Count'),0), not(equals(outputs('Compose_Last_Day'), outputs('Compose_Today'))))

{ "assignee": { "accountId": "@variables('varEscalationAssignee')" } }

@concat(variables('varJiraBaseUrl'), '/browse/', items('Apply_To_Each_Issue')?['key'])

Customize & download