Set up and manage your changelog

Use a changelog to show customers what is new, improved or fixed. You can write updates yourself, use work already tracked in ProductLift, or draft release notes from Git commits.

If you do not have a changelog yet, create one under Settings → Boards → Create board → Changelog.

Write your first update

Create a changelog post, explain the change and check it in the customer view. You can publish now or schedule it for later.

If you already have release notes in another tool, import your changelog instead of copying each entry yourself.

Choose how to prepare release notes

What you have What to do
A new feature, improvement or fix to announce Write a changelog update
Several roadmap items in one release Link them to one release note
A list of Git commits from your developer Draft release notes with Git2log
A customer request that has been delivered Update the request and notify its followers

Organize releases and versions

For a numbered release, add a Version such as 2.4.1 to its posts. For a named launch, use Release, such as Spring release.

Group your changelog by month, version or release, and choose cards or a timeline. ProductLift can split large groups into categories. Grouping brings separate posts together on the page; it does not merge them into one post.

Choose who gets an email

Use Notify subscribers on an entry to announce it to changelog subscribers. Use Email followers when changing a feedback item's status to update people following that request.

These are separate messages. Check both choices when feedback moves to the changelog, including when you want to publish without sending email.

Publish in your customers' languages

Enable your portal languages and automatic post translation to translate new changelog posts. You can also translate older posts and review translations after editing the original. AI translations use credits; text inside images is not translated.

Put updates where customers will see them

Share the changelog link, add a changelog widget inside your app, or offer the RSS feed. Before sharing, use Preview as customer to check the layout, release groups and links.

Add detail and connect your tools

Use formatted text, video and attachments when an update needs more explanation. For a change that needs a full how-to, draft a knowledge-base article from the changelog entry.

Your developer can create and update release notes through the API, use webhooks for related actions, or connect an AI assistant through MCP.

After sending an announcement, check delivery history. It shows supported delivery and click events, not proof that a person read the message. Personal activity digests summarize unread notifications; they are not a scheduled newsletter of selected changelog posts.