Turn Jira tickets into release notes
Filter the closed issues for the release with JQL, paste them into the Jira to Markdown converter, then run the result through the release notes generator. You get one Markdown draft that converts cleanly back into Jira wiki markup, Confluence, or Slack.
The chain
- 01
Filter the release scope in Jira
Build a JQL filter for the issues that shipped — fix version, sprint, or a resolved-date window.
You get: A JQL query you can paste into Jira's issue search.
- 02
Pull the tickets out as Markdown
Copy the issue keys, summaries, and descriptions out of Jira and paste them in. Jira wiki markup converts to clean Markdown.
You get: A Markdown list of everything in the release.
- 03
Draft the release notes
Paste the Markdown ticket list. Use the prompt below if you want to run the same step in Claude or ChatGPT instead.
You get: Release notes grouped by what changed, written for users rather than for the board.
- 04
Ship it to where people read it
Convert the draft once and copy the version you need — Jira wiki markup for the release ticket, Confluence for the docs space, Slack mrkdwn for the announcement.
You get: The same notes in every destination format, formatting intact.
The prompt for the thinking step
Release notes from a ticket list
Paste your Markdown ticket list where the placeholder is. Works in Claude, ChatGPT, or any assistant.
You are writing release notes for people who use the product, not for the engineers who built it. Here is the list of tickets that shipped in this release: <tickets> [PASTE YOUR MARKDOWN TICKET LIST HERE] </tickets> Write the release notes in Markdown with these rules: 1. Group items under these headings, and drop any heading with nothing under it: New, Improved, Fixed. 2. One line per item. Lead with what the user can now do, not with the ticket title. 3. Keep the ticket key in parentheses at the end of the line so anyone can trace it back. 4. Skip internal refactors, dependency bumps, and test-only changes unless they change behavior a user can see. 5. No marketing adjectives. If an item is small, let it read small. 6. If a ticket is too vague to describe in user terms, list it at the bottom under "Needs a better description" instead of guessing. Start with a two-sentence summary of the release before the headings.
Run it now
Paste commit messages or PR titles, get customer-facing release notes grouped into New, Improved, and Fixed. Free, no login.
Open the release notes generatorQuestions people ask
Can I generate release notes straight from git instead of Jira?
Yes. Paste your commit log into the release notes generator instead of the ticket list. If your commits follow Conventional Commits the grouping comes out cleaner, and the conventional commit generator can help you get there going forward.
Do my tickets get sent anywhere?
The JQL builder and the Jira to Markdown converter run entirely in your browser. The release notes generator is AI-backed, so that step sends your pasted text to Amazon Bedrock. See the privacy page for what is logged and for how long.
How do I paste the result back into Jira without losing formatting?
Jira does not accept Markdown in issue descriptions. Run the draft through the Work Formatter and copy the Jira wiki markup version, which converts headings, lists, code blocks, and tables to the syntax Jira expects.
What if the release spans several sprints?
Filter on fix version rather than sprint in the JQL builder. That captures everything tagged for the release regardless of which sprint closed it.
More tools for “Ship release notes”
Turn merged commits and closed tickets into release notes your users, your team, and your changelog can all read.