Turn a batch of shipped tickets into clear, customer-friendly release notes, organized into highlights, improvements, and fixes, and written in your product's own voice.
For
Product Managers
Product Marketers
Engineering Leads
Developer Relations
Sample prompt to Joy's Assistant
Turn these shipped tickets into customer-friendly release notes for [product]: [tickets]. Group them into highlights, improvements, and fixes, and write them in our product's voice.
What it can look like
An illustrative example. Your output will reflect your own sources, data, and prompts.
Turn these shipped tickets into customer-friendly release notes for Orbit: ORBIT-402 saved filter presets on the dashboard, ORBIT-418 CSV column order now matches the on-screen table, ORBIT-425 dark mode for the report viewer, ORBIT-431 fixed a crash when opening a report with no data, ORBIT-440 faster dashboard load from caching recent queries, ORBIT-447 fixed timezone labels showing the wrong offset. Group them into highlights, improvements, and fixes, and write them in our product's voice.
Here are the release notes for this Orbit update, grouped into highlights, improvements, and fixes and written in the plain, friendly style your past notes use. I led with saved filter presets since it's the change users have asked for most.
Orbit release notes (draft)
Release: Orbit 4.3 Date: July 4, 2026
Same release, three framings. The customer notes lead with saved filter presets since it's the change users have asked for most; the in-app blurb trims it to a few lines; and the internal version arms sales and CS with the angle to lead on. Switch between them below.
This release is all about getting to your data faster, starting with a feature a lot of you have asked for.
Highlights
Saved filter presets. Set up the filters you use most and apply them to any dashboard in a single click, so you're not rebuilding the same view every morning.
Dark mode for the report viewer. Easier on the eyes for late-night analysis, and it matches the rest of your workspace theme.
Improvements
Faster dashboards. Recent queries are now cached, so the dashboards you visit often load noticeably quicker.
Cleaner CSV files. Columns in a saved CSV now come out in the same order as the table on your screen.
Fixes
Empty reports no longer crash. Opening a report with no data now shows a friendly empty state instead of an error.
Correct timezone labels. Time offsets now display the right zone wherever you're working.
Trimmed to a few lines for the what's-new panel, leading with the headline change.
Saved filter presets. Apply your go-to filters to any dashboard in one click.
Dark mode arrives for the report viewer.
Dashboards load faster, CSV columns now match your screen, and the empty-report crash and timezone labels are fixed.
A "See full notes" link opens the complete changelog for anyone who wants the detail.
The same release framed for the people who have to talk about it, so sales and CS lead on the right thing.
For customer conversations, the headline is saved filter presets: our most-requested dashboard feature this quarter, and a clean reason to re-open accounts that asked for it. Pair it with the caching work: frequently visited dashboards now load noticeably faster, which lands well with power users running heavy reports.
Talk track. Lead with presets and speed; both answer the adoption friction admins flagged in recent QBRs.
Retention angle. The empty-report crash and the timezone-label bug both generated support tickets. Worth proactively telling affected accounts they're resolved.
Dark mode is a nice-to-have, not a lead. Mention it if it comes up; don't build the pitch on it.
All three describe the same six shipped changes: what moves is the emphasis and the level of detail, not the facts.
Want a shorter in-app version for the what's-new panel, or a social post announcing the new presets?
From shipped tickets to published notes
Release Notes Generator takes the tickets you shipped, terse titles, internal codes and all, and rewrites them as release notes a customer can follow. Joy groups the changes into highlights, improvements, and fixes and matches the voice of your past notes.
Paste the shipped tickets
Drop in the tickets from the release, titles, IDs, and any notes. Joy reads them as they are; no cleanup needed.
Say who it's for and the voice
Ask for customer-friendly release notes and, if you like, point Joy at past notes so it matches your product's voice.
Review the draft
Get notes grouped into highlights, improvements, and fixes, with each change rewritten in plain language. Adjust what gets top billing.
Publish where you publish
Ask for a tweak, "make the intro warmer" or "drop the internal IDs," then copy the notes into your changelog, app, or customer email.
Make it one click for your team
Save this ask as a custom command on the assistant your team already uses, connect it to your past release notes, and anyone can turn a release into notes in one click.
Make it yours
Highlights First
Joy leads with the changes customers care about most, not the order the tickets came in.
Your Product's Voice
Point it at past notes and the tone carries over, so every release sounds like you.
Jargon Removed
Internal codes and ticket-speak get rewritten into language a customer can follow.
Sorted for You
Every change lands under highlights, improvements, or fixes automatically.
Email Announcement
Reshape the notes into a release email for your customer list.
In-App What's New
Condense to a few lines for an in-app what's-new panel.
Developer Changelog
Keep the technical detail for a version aimed at API users.
Multi-Product
Split one release into separate notes per product or plan.
Frequently Asked Questions
How do I write release notes from Jira tickets?
Paste the shipped tickets, titles, IDs, and any notes, and ask Joy for customer-friendly release notes. It rewrites each ticket in plain language and groups the changes into highlights, improvements, and fixes for you to review and copy.
Can it match our product's tone of voice?
Yes. Point Joy at your past release notes and it picks up your tone, whether that's playful, straightforward, or technical, so a new release sounds like the ones before it.
How does it decide what's a highlight?
Joy leads with the changes customers are most likely to care about, such as new features and noticeable improvements, and keeps smaller fixes lower down. You can promote or demote anything with a quick follow-up.
Will it remove internal codes and jargon?
Yes. Internal ticket IDs and engineering shorthand get rewritten into language a customer can follow. If you want the IDs kept for a developer-facing version, just ask.
Can I get different versions for email and in-app?
Yes. From the same set of tickets, ask for a full changelog, a short in-app what's-new blurb, or a customer email, and copy each version into the right place.
