Shri and Robin here, cofounders of Chapter.

As a former Product Manager and CTO we know the importance of creating changelogs both for internal alignment, and for customers to be informed of our latest updates.

But writing them (frequently) always felt like an annoying task, knowing what to include in the changelog, and how to maintain brand voice never came easy.

When done well, the story within the changelog can be used to build momentum and celebrate achievement, even activate dormant users.

With Chapter you can auto-generate user-facing changelogs using your existing Linear tickets, and corresponding PRs. Simply add the comment “@chapter” within a ticket in your current cycle, and get a changelog entry back. Each entry will include sections for major features, a list of improvements, a list of fixes, and contributors for each. We’re even placing your UI over nicely designed background gradients if you include a Figma link within your ticket.

You can watch a demo (2 minutes) here(https://www.loom.com/share/713892cf988c4e9e9a53aad97f62d402?...).

We’d love to hear what you think, and if you’d like to use Chapter with your team. Happy to get the service running for you.

Feel free to reach out to us directly here(https://calendly.com/run-nectar/15min).