Jira Release Notes Generator

Overview

This flow automates release-note creation and distribution from Jira. On a schedule it gathers every issue in a configured release (project + fixVersion), groups them into Features & Enhancements, Fixes, and Breaking Changes, renders a formatted HTML release-notes document, publishes it to a SharePoint document library, and announces the release to a Microsoft Teams channel.

Why it matters: writing release notes by hand is slow and inconsistent. Generating them straight from Jira guarantees complete, uniform, on-time notes with zero manual effort.

Ships Off (Stopped) as a reference demo. Requires a SharePoint document library for the notes.

Use Case

A delivery team marks a Jira version as released and wants polished release notes produced and distributed automatically - saved to SharePoint for the record and posted to Teams for the team and stakeholders.

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.

Target a different release

Set flowlibs_ReleaseProjectKey and flowlibs_ReleaseVersion; the JQL rebuilds automatically.

Add a release-note gate

Extend the JQL with AND labels = release-note to include only flagged issues.

Customer vs internal notes

Duplicate the Compose + CreateFile pair to emit a customer-facing version into a second library.

Trigger on actual release

Replace the Recurrence trigger with a Jira webhook / When a version is released trigger when available; the compile-and-publish body is unchanged.

Publish elsewhere

Swap Create Release Notes File for a Confluence or HTTP publish action.

Email customers

Add an Outlook SendEmailV2 after the Teams post using the same release-notes HTML body.

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 fixVersion = "', variables('varReleaseVersion'), '" ORDER BY issuetype ASC, priority DESC')

contains(toLower(string(item()?['fields']?['labels'])),'breaking')

<li><strong>@{item()?['key']}</strong> - @{item()?['fields']?['summary']} <em>(@{item()?['fields']?['status']?['name']})</em></li>

concat('Release-Notes-', variables('varProjectKey'), '-', variables('varReleaseVersion'), '-', formatDateTime(utcNow(),'yyyyMMddHHmm'), '.html')

length(body('Get_Release_Issues')?['issues'])