Release notes template generator
Paste your issue list or a Jira CSV export and the tool groups it into New features, Improvements and Bug fixes, with a version heading, then outputs Markdown, HTML or plain text. Issue keys can link back to your Jira site.
Everything runs in your browser. Your text and files stay on your device and are never uploaded.
Put the type in brackets at the end, or start with fix: or feat:. A CSV needs Summary and, optionally, Issue key and Issue Type columns.
How to use it
- Paste one issue per line, such as PROJ-101 Add CSV export [Story], or open a Jira CSV export.
- Enter the version, the date and an optional one-line intro.
- Add your Jira browse URL if you want each issue key to be a link.
- Choose Markdown, HTML or plain text and check the grouping.
- Copy the result into Confluence, a README, a GitHub release or an email, or download it as a file.
A release notes template that works
Readers scan release notes for two things: what they can now do and what stopped breaking. Lead with new features, then improvements, then bug fixes, and keep each line to one sentence that starts with the user-visible result.
| Jira issue type | Section |
|---|---|
| Story, Epic, Feature, New | New features |
| Improvement, Task, Sub-task, Enhancement | Improvements |
| Bug, Defect, Hotfix, Incident | Bug fixes |
| Anything else, or no type | Other changes |
Questions
What should a release notes template include?
A version and date, a one-line summary, then sections for new features, improvements and bug fixes. Each entry is one sentence about what changed for the user, with an issue key for traceability.
How does the tool decide which section an issue goes in?
It reads the issue type from brackets at the end of the line, such as [Bug], a prefix like fix: or feat:, a heading above the lines such as Bug fixes:, or the Issue Type column of a CSV. Bug, Defect and Hotfix become Bug fixes. Story and Feature become New features. Task and Improvement become Improvements. Anything else goes under Other changes.
How do I export issues from Jira to paste here?
Run a search for the version, for example fixVersion = 2.4.0, then use Export and choose CSV. Open the file here or paste its contents. Summary is required, Issue key and Issue Type are used when present.
Can I paste the notes into Confluence?
Yes. Paste the Markdown output into a Confluence Cloud page and the editor turns the headings, bullets and links into formatted content. Use the HTML output for a web page or a help center article, and plain text for email or chat.
Are my issue titles sent anywhere?
No. Parsing and formatting happen in your browser, so internal ticket titles stay on your device.