26 October 2026 · 6 min read
How to send release notes to clients automatically
How agencies can generate client release notes from the tickets they shipped, write them in plain words, and send them by email and the client portal.
Quick answer
To send release notes to clients automatically, generate them from the tickets in a version or deployment rather than writing them by hand. Write ticket titles a client can understand, keep internal work out of client-facing releases, then email the summary to chosen contacts and publish it in their portal when the release is complete.
Release notes are the cheapest client update an agency can send. They show the work you delivered, they cut the "any news on this?" emails, and they give account managers something concrete to talk about. Yet most teams still write them by hand at the end of a release, so they arrive late or not at all.
The fix is to stop writing release notes and start generating them from the tickets you already shipped. This guide explains how, using a fictional client, Northwind Logistics.
Why do clients care about release notes?
Clients pay for outcomes they can't always see. A fixed bug in a background job, a faster report or a new export button may go unnoticed for weeks. A short release note turns that invisible work into a visible record.
For an agency, a regular release note also:
- answers "what did we get this month?" before anyone asks it
- tells the client's own team what changed, so they don't raise a ticket about new behaviour
- gives you a dated history when a client asks "when did that change?"
- shows the requests they raised were actually delivered
What should a client release note include?
Keep it short. A client reads a release note in under a minute, often on a phone. A good structure has four parts:
- The release name and date, for example "Northwind portal 2.4, released 27 October".
- What's new: features the client will see, one line each.
- What's fixed: bugs, ideally linked to the ticket the client raised.
- Anything they need to do: new settings, training, or a change in behaviour.
Leave out the technical detail. Clients don't need the branch name, the database migration or the library you upgraded.
How do you generate release notes from tickets?
The principle is simple: every change that reaches production should already be a ticket, so the release note is a filtered list of those tickets.
That works when three things are linked:
- Tickets to code. Commits and pull requests mention the ticket key, such as NW-142, so you know which tickets are in the build.
- Code to deployments. Your CI pipeline records each deployment with its environment, version and the tickets it included.
- Deployments to a version. Tickets are grouped into a version, and the version is marked complete when it ships.
With those links in place, the list of tickets in a release is a fact, not something someone reconstructs from memory. Here is a fictional Northwind release:
| Ticket | Type | Title | In client note? |
|---|---|---|---|
| NW-142 | Bug | Delivery dates now show in the client's time zone | Yes, under Fixed |
| NW-147 | Feature | Export delivered orders to CSV | Yes, under New |
| NW-151 | Feature | Filter the orders list by depot | Yes, under New |
| NW-153 | Bug | Search no longer misses orders with a hyphen in the reference | Yes, under Fixed |
| NW-155 | Internal | Upgrade the PDF library | No |
| NW-156 | Internal | Add tests for the order import job | No |
| NW-158 | Bug | Password reset email no longer goes to spam for some domains | Yes, under Fixed |
Seven tickets shipped. Five belong in the client's note. Two are internal and stay out.
How do you write ticket titles a client can read?
Generated release notes are only as good as the ticket titles. "Fix TZ bug in DeliveryDateFormatter" is fine for a developer and meaningless to a client. "Delivery dates now show in the client's time zone" works for both.
A few habits make generated notes readable without editing:
- Describe the result, not the code. Write what the user sees after the change.
- Use the client's words. If they call them "depots", don't title the ticket "warehouse nodes".
- Fix the title when the work is done. Titles written at triage often describe the symptom. Update them before the ticket closes.
- Use ticket types. Separate bugs, features and internal work, so internal tickets can be left out of client releases.
This takes seconds per ticket. It saves an hour of rewriting at release time.
How do you send the release notes automatically?
There are a few common approaches, each with trade-offs.
GitHub's generated release notes. GitHub can generate release notes for a repository release, listing merged pull requests, contributors and a link to the full changelog. You can group or exclude pull requests by label with a .github/release.yml file (GitHub Docs). This is excellent for developers and open-source projects. It's written from pull request titles, though, and it lives in GitHub, where most clients never look.
Jira's release notes. Jira Cloud generates release notes from the work items in a version, grouped by work type, and lets you choose which fields to include. You can copy them as markdown or HTML, save them to the version, or publish them as a Confluence page, and Rovo can help draft a summary. Atlassian's guide, checked on 26 October 2026, doesn't describe emailing them to customers (Atlassian Support). To reach a client, you would paste them into an email or use a separate tool. If you already run Jira and Confluence, this is a solid option.
Release notes in the same tool as the client's requests. If your client portal, tickets and deployments live in one product, the release note can go straight back to the people who raised the requests. That's the approach Jonta takes.
How does Jonta send release notes to clients?
In Jonta, the client's request is the development ticket. It picks up commits and pull requests from GitHub, is recorded in a deployment, and belongs to a version. Release notes are generated from the tickets in a version or deployment.
When the release is ready:
- Mark the release complete.
- Email the summary to the client contacts you select.
- Publish the release in the client portal, where clients can see releases alongside their own requests.
Because the notes come from the same tickets the client raised, a client who reported NW-142 can see it in the published release 2.4. Nobody had to write an email to tell them. Deployments can be reported automatically from your CI pipeline or recorded manually, so the version always reflects what actually shipped (GitHub and deployments).
Release notes, the client portal, GitHub integration and deployment tracking are included on every plan. Jonta is free for up to 10 users, and Pro is £25 a month for your first 6 months, then £50 a month for up to 50 users, flat. See pricing for the other plans.
How often should you send release notes?
Match the client's release rhythm, not every deployment. A typical agency pattern:
| Situation | Suggested cadence |
|---|---|
| Two-week sprints, one release per sprint | Every 2 weeks |
| Continuous deployment, several deploys a day | Weekly summary |
| Retainer with occasional changes | Monthly, or whenever a version completes |
| Urgent fix for a client-reported bug | Same day, as a short note |
Consistency matters more than frequency. A note every two weeks that always arrives beats a detailed note that turns up whenever someone remembers.
A simple checklist
Before you send your next release note:
- Every shipped change has a ticket, and every ticket is in a version.
- Ticket titles describe what the client sees.
- Internal tickets are a separate ticket type and stay out of the note.
- Bugs the client reported are clearly listed as fixed.
- The note says whether the client needs to do anything.
If you'd like to see generated release notes and the client portal with a fictional project, book a demo or request a free workspace.
Questions people also ask
Can Jira create release notes?
Yes. Jira Cloud generates release notes from a version's work items, which you can copy as markdown or HTML or publish to a Confluence page. Atlassian's guide (checked 26 October 2026) doesn't describe emailing them to customers, so you would paste them into an email or use another tool to send them.
How often should an agency send release notes to a client?
Once per release the client would notice. For most agencies that is every one to two weeks, matching the sprint or deployment cadence. Batch tiny fixes into the next release rather than sending a note for every deployment.
Should clients see every ticket in a release?
No. Leave out internal work such as refactoring, dependency updates and test changes. Clients want to know what changed for them, what was fixed and whether they need to do anything.