Skip to main content

Compile Release Notes Automatically With AI

By the end of this recipe you'll have an automation that, at the end of every sprint, gathers everything you shipped from your board, drafts polished release notes grouped into New, Improved, and Fixed, and drops them in a document for a person to review and publish. Writing release notes is a chore because the information is already there — scattered across the rows you closed this sprint. Because your shipped work and your team chat live in the same workspace, the AI can read that real activity and narrate it, instead of you reconstructing the release from memory on a Friday afternoon.

Readiness: Available now (built as one Automation). The version where a single named teammate owns the release-notes ritual end to end — compiling, drafting, and nudging you to publish — is rolling out in early access.

What it does​

The release-notes compiler is one automation with a human in the middle:

  1. It runs on a schedule — say, 4:00 PM on the last day of each sprint (or every Friday, or on the first of the month for a monthly changelog).
  2. It gathers what shipped from your board: the rows that reached a Shipped, Released, or Done status since the last edition. You can pull from one board or from several (product, mobile, platform) in the same run.
  3. It drafts the notes with an AI step — a version header, a short intro, and sections grouped by New, Improved, and Fixed — each item rewritten in plain, customer-facing language, not the raw internal ticket title.
  4. It saves the draft as a document in your Releases folder and pings the release owner with the link.
  5. A human reviews, polishes, and publishes. The AI does the gathering and the first draft; a person still signs off on the wording before it reaches customers.

Keeping the publish step in human hands is what makes this safe to run unattended every sprint — the tedious part (finding what shipped, writing the first pass, grouping it) is automated, and the judgment call stays with you.

Build it yourself​

One-time setup​

Prepare the board your work already lives on

You don't need a new board — you need the one where engineering work is tracked to carry three things the compiler reads:

  • Status — with a terminal value the release is built from, such as Shipped, Released, or Done.
  • Type (or Category) — New, Improved, Fixed (add Security or Deprecated if you use them). This is what the notes group by.
  • Shipped Date — a date column the compiler filters on so each edition covers exactly one period.

If items reach "shipped" without a reliable date, add a tiny helper automation: a Field changed trigger watching Status, and a Set date to now action that stamps Shipped Date the moment a row flips to Shipped. Now the compiler's date filter is always accurate.

The automation​

Trigger: Schedule

In Automations, start a flow with a Schedule trigger set to your release cadence — for example, 4:00 PM on the last day of each sprint. This one trigger is what turns release notes into a standing ritual instead of a task someone remembers to do.

Action: Find this release's shipped rows

Add a Find rows action on your board that returns the rows for this edition — for example, where Status is Shipped (or Released/Done) and Shipped Date is in the last two weeks. Use a row filter to combine those conditions. Shipping across several boards? Add a Find rows step per board — one for web, one for mobile, one for platform — so a single run covers the whole release.

Transform: Assemble the list

Add a Join transform to combine the found rows into one clean, readable list the AI can work from. Prefer to control each line's shape (say, [Type] Title — description)? Use a templating transform instead, so every item arrives to the AI in a consistent format.

AI step (optional): Classify each item by type

If your board doesn't already have a Type column, add an AI → Classify step that sorts each item into New, Improved, or Fixed. Skip this step if your rows are already typed — the Generate step can group by your existing column directly.

AI step: Draft the release notes

Add an AI → Generate step that writes the notes from that list: a version header, a one-paragraph intro on the theme of the release, and a section per type with each change as a plain-language bullet. Give it your voice in the prompt — "benefit-first, no internal jargon, second person, ~250 words" — so the first draft already reads like your changelog. Want it in more than one language? Add an AI → Translate step to produce a variant for each locale.

Action: Save it as a document for review

Add a Create document action that saves the draft into your Releases folder. This is the release owner's editable working copy — the AI's first pass, ready for a human to tighten and approve.

Action: Tell the team it's ready

Add a Post channel message action to your #product or #releases channel — "📝 v2.4 release notes are drafted and ready to review" with the document link pulled from the previous step. Prefer to ping one person? Use a Send direct message to the release owner instead.

tip

Announcing to customers, not just the team? Keep the send behind a human. Add a Send or draft email action in draft mode pointed at your stakeholders, or a human approval request step that pauses the automation until someone approves — so the internal draft is automated, but nothing external ships until a person signs off on the wording.

Or just ask Copera AI​

You don't have to assemble the graph by hand. Open Ask Copera AI and describe it:

"On our Engineering board, add a Shipped Date column and a Type column with New, Improved, and Fixed. Then build an automation that on the last day of every sprint finds everything shipped in the last two weeks, drafts release notes grouped by type in plain customer-facing language, saves them as a document in our Releases folder, and posts a message in the #product channel with the link so I can review and publish."

Ask Copera AI can create the columns, then assemble the automation for you. With the default Ask before acting permission mode, it shows a review card for each change before anything is created — so you approve the columns and the automation before they exist. See What Copera AI Can Do for the full list of what it can build.

Want the notes right now instead of on a schedule? Ask on demand: "Read our Engineering board and write release notes for everything marked Shipped this sprint, grouped into New, Improved, and Fixed, then save it as a document." It reads the board, drafts the notes, and — with Ask before acting on — shows you the draft on a review card, with a Sources list of exactly which rows it drew from, before it creates anything.

Make it a standing teammate​

Early access

Standing AI teammates are rolling out gradually. When one is available in your workspace, you can put a single named teammate — a "Release Manager" — in charge of the whole ritual: it watches items reach Shipped across your boards through the sprint, drafts the release notes for review, saves them as a document, and posts an internal heads-up that they're ready, all on its own schedule and under its own identity. Customer-facing publishing stays with a human — a teammate drafts and posts inside your workspace but never sends externally on its own. If you don't see teammates yet, they're on the way — everything in this guide can be built today as an Automation.

Tips​

tip

Give each row one good sentence. The notes are only as good as the rows underneath them. A row titled "Fix" produces a weak bullet; a row whose description says what changed and who it helps produces a great one. The AI rewrites for tone, but it can't invent the substance — a clear row body is the highest-leverage habit for good release notes.

tip

Scope each edition with a Version column. Add a Version column and stamp it when work ships (a Set field action on your helper automation does this). Then the compiler's Find rows filter can pull "everything tagged v2.4," so an edition maps cleanly to one release instead of a rolling date window.

tip

Draft to yourself first, then flip it on. Point the announcement at your own DMs for the first couple of sprints. Once the notes read the way you'd write them, change the destination to your #product channel and let it run unattended.

tip

Compile from your release meeting, too. If you run a sprint review, trigger a companion automation on Transcription complete, add a Load meeting context step and an AI → Extract step to pull the "what we shipped" moments out of the conversation, and fold those into the draft. Now the notes reflect both the board and what the team actually called out in the room. See Meeting Transcription.

tip

Set a spend cap. Because the Generate step (and any Classify or Translate) draws on AI usage, give the automation a per-automation spend cap so a heavy release can never run past a budget you choose. The usage dashboard shows exactly where credits go.

Frequently Asked Questions​

Can Copera compile release notes automatically?​

Yes. A scheduled automation uses a Find rows action to pull everything you shipped this period, an AI Generate step turns those rows into polished notes grouped into New, Improved, and Fixed, and a Create document action saves the draft. It can also post an announcement to your product channel. Because your shipped work already lives on a board, the AI writes from real data.

Does it write customer-friendly notes or just list ticket titles?​

It rewrites them. The AI Generate step takes your internal titles and descriptions and produces plain, benefit-first language grouped by type, with a version header and a short intro — not a raw list of ticket names. You set the voice in the prompt.

Where do the shipped items come from?​

From your board — the rows that reached a Shipped, Released, or Done status, filtered by a shipped date. Point the Find rows step at your issue tracker board, your product board, or a dedicated Releases board. One run can span several boards.

Can I review the notes before they're published?​

Yes, and it's the recommended pattern. Create document saves an editable draft, an email can be prepared in draft mode instead of sent, and a human approval request step can pause the automation until someone signs off — so nothing customer-facing goes out unreviewed.

Can it group changes by type and version?​

Yes. If your board has a Type column, the notes group by it directly; if not, an AI Classify step sorts each item into New, Improved, or Fixed first. Add a Version column and filter on it so each edition covers exactly one release.

Can it build release notes from my GitHub activity?​

Copera compiles release notes from your board — the rows you mark shipped. If you track engineering work in Copera (or mirror your issues onto a board), the compiler has everything it needs. The GitHub connector can create issues from an automation, but reading pull requests to auto-generate notes isn't available yet, so your board is the reliable source. See Connectors.