Use this template to turn a selected Jira release into a customer update. Group shipped work by its value to the reader, then verify availability and remove internal details before publishing.

Copy the template

Word Markdown

[Product] release notes

Release: [Jira version or release name] | Available: [Date]

[The main customer benefit of this release.]

New features

• [Customer-facing feature name]: [Benefit]. [How to use it].

Improvements

• [Workflow]: [What changed for the customer].

Bug fixes

• Fixed [observable problem] when [trigger].

Availability and action required

[Which customers can use this release, rollout limits, and any required action.]

Help

[Link to customer documentation or support].

From Jira issues to a readable update

The following fictional tickets belong to Northstar 2.8, a reporting app release. They illustrate editorial choices, not a live customer release.

• NORTH-142 — Persist report filter state: a shipped story that lets people save report filters as a named view.
• NORTH-156 — Add range to CSV filename: a shipped improvement that helps people identify downloaded reports.
• NORTH-161 — Fix inclusive end-date export: a shipped bug fix for exports that omitted the last selected day.
• NORTH-164 — Refactor export worker: internal maintenance with no separately confirmed customer-visible change.

The first three issues belong in this update. The refactor does not need its own public bullet. If several issues support the saved-view feature, combine them into one explanation instead of listing each ticket.

Completed Jira release notes example

Northstar 2.8 — saved report views

Available September 8, 2026

Save your report filters as a named view so you can return to the same report setup next week.

New features

Open a report, choose your filters, and select Save view. Saved views are available to all workspace members.

Improvements

CSV filenames now include the selected date range, making downloaded reports easier to identify.

Bug fixes

Fixed an issue where CSV exports could omit the final day of a selected date range.

Availability

Available to all workspaces. Refresh your browser to see the update. Saved views do not yet preserve column widths.

Notice how the update replaces “persist filter state” with an action a customer can take. The issue keys remain useful for internal review, but the customer update does not require access to Jira.

Select the right work first

Choose the version or set of issues that corresponds to the release. Confirm that the selected work is deployed and available to the audience. “Done” is a workflow status; it is not sufficient evidence that every customer can use a feature.

Check issue descriptions for customer-visible behavior and limitations. If a ticket only describes the implementation, ask the feature owner for a plain-language explanation and usage steps. Do not infer a performance improvement from a refactor or invent a workaround for a bug.

Remove private customer names, credentials, internal links, and details that are inappropriate for the public update. Keep an internal issue-to-note mapping for review if your team needs traceability.

Set up the template in Released

1. Open your workspace’s Settings → Templates and select Create.
2. Start from an existing template or create one from scratch. Add the headings you need from the copyable template above.
3. Use an Issue sections AI block for work that needs a heading and explanation. Use an Issue lists block for concise bug fixes. Configure the work types or filters to match your Jira setup.
4. Create a post using the template and the intended selection of work. Review the generated draft for accuracy, duplicates, and audience fit.
5. Add screenshots to the generated post, check availability and links, then publish the approved update.

A Word or Markdown download does not import these AI blocks into Released. Configure them in the template editor using the Released template documentation.

When Jira’s built-in release notes are enough

Jira Cloud can generate release notes for a version, categorize work by type, and copy the result as Markdown or HTML. This is useful when you need a straightforward record of version contents. See Atlassian’s release notes instructions.

For customer communication, review the output for jargon, duplicate changes, private details, and missing availability information. Released adds a workflow for drafting, editing, and publishing those customer updates from selected Jira work.

Adapt the update for another audience

Use the internal release notes template when colleagues also need rollout checkpoints and escalation guidance. Use the email template for a short announcement that links to the published update. The general template guide explains which sections to keep for each release.

Publish release notes your customers will read

Select shipped Jira work, turn it into a clear draft, and publish the approved update where customers will find it.

Try Released in Jira →