A changelog your users actually see. And one that closes the loop.
Publish release notes in minutes, then automatically tell the people who asked for it that it shipped. The same widget that collects feedback shows a "new updates" badge — so the loop closes itself.
Shipping in silence is a waste.
You built the thing they asked for. Then you told nobody. The request sits open, the customer assumes it never happened, and your best work goes unnoticed. A changelog wired to your feedback turns every release into a reason for users to come back.
Everything a changelog tool should do.
Write dated entries in Markdown — title, body, screenshots, optional version. Save a draft, publish when it's ready.
Ship an entry linked to a request and everyone who voted or asked for it hears about it. No manual list to chase.
The widget shows a small "new" badge when there's an update users haven't seen. They notice without an email.
Every entry connects to the original feedback posts it resolves — and those posts can auto-mark as Shipped.
Write Friday, publish Tuesday. Schedule an entry for a future date and it goes live on its own.
The changelog lives on your portal with your logo and colors — not a generic third-party page.
From shipped to seen, automatically.
When a feedback post moves to Shipped, "Promote to changelog" appears — title, body, and link pre-filled.
Edit the draft, then publish now or set a future date. Drafts and scheduled entries stay hidden until then.
Everyone who voted gets the "your post shipped" notification, and the widget badge nudges the rest.
A changelog that closes the loop.
Entries link back to the requests they resolve, so shipping and announcing are one motion — not two.
The users who voted hear it first, automatically. You write once; Feedjolt tells everyone who asked.
The widget's "new" badge surfaces updates where users already are — not buried in an inbox.
Voting, roadmap, and changelog together — not three separate subscriptions stitched by hand.
Frequently asked, plainly answered.
What is changelog software?
Changelog software lets you publish a public "what's new" feed of product updates and release notes. Feedjolt links each entry back to the feedback that prompted it and notifies the users who requested or voted for it — so announcing a release is part of closing the loop, not a separate chore.
Does it notify customers when I ship something?
Yes. When you publish an entry linked to a feedback post, everyone who voted on or requested it gets a "your post shipped" notification automatically — no manual list to compile.
How do users see updates inside my product?
The Feedjolt widget shows a small "new" badge when there's an update a user hasn't seen yet, so they notice it where they already work — no email required.
Can I schedule a changelog entry for later?
Yes. Save entries as drafts and schedule them for a future date. Drafts and scheduled entries stay hidden from the public changelog until they go live.
Does Feedjolt write changelogs with AI?
No. You write your release notes in Markdown — Feedjolt doesn't auto-generate the copy. What it automates is the loop: linking entries to requests, notifying voters, and surfacing the update in the widget.
Can I match the changelog to my brand?
Yes. The changelog lives on your Feedjolt portal with your own logo and colors, alongside your feedback board and roadmap — not on a generic third-party page.