Release Notes

Use release notes to turn shipped work into a clear narrative for customers, stakeholders, or internal teams.

Release notes are generated from actual work: completed tasks, merged pull requests, resolved issues, initiative context, comments, and taxonomy. They are workspace-level summaries for one or more teams over a selected time range.

What release notes contain

Release notes are editable summaries of what shipped in a selected period. Each note has a title, rich-text content, audience, associated teams, time period, creator, and creation time.

Audiences can be internal, external, or executive. Edit the generated content before sharing so the note matches the audience and emphasizes outcomes for readers who do not need implementation detail.

Sharing

You can copy release note content as Markdown or send it to another tool. The format is useful for Slack, docs sites, email, changelogs, and stakeholder updates.

Generate separate release notes for separate audiences when the same shipped work needs different framing:

Audience	Emphasize
External	User-facing changes, improvements, and product value without internal implementation detail.
Internal	Implementation notes, resolved blockers, decisions, and next steps.
Executive	Outcomes, risk, customer impact, and strategic progress.

Source work

Good release notes depend on clean source work: completed tasks, completed initiatives, pull requests, taxonomy, and comments that explain what changed and why.

Private tasks are excluded. If important shipped work is private, make sure the public summary has enough team-visible context before generating the note.

Use Stakeholder Updates when release notes need to become a broader status narrative.