Publishing a changelog entry

Your changelog is where you say what you shipped. The part that makes it worth keeping is the link back to the feedback it answers: close a post with an entry and everyone who voted for that post hears about it.

Open Changelog in your workspace and press New entry.

Write it

An entry has a title, a body in markdown, and a category — Added, Fixed, Improved, or whatever you rename them to on the Settings tab.

Who is this for? decides where it appears. Everyone is a company-wide announcement and shows on every changelog you have. Picking one board makes it that product's release, and it appears on that board's changelog only.

Link the feedback it closes

Search for the posts this entry ships and attach them. For each one you choose the status to move it to — your own set, in your own words, with Shipped preselected if you have one.

Publishing then does three things at once: the entry goes live, those posts move to that status, and the people who voted for them are emailed. The publish button tells you how many before you press it, because it cannot be undone.

Boost, or not

Boost is one switch and it decides who hears about the entry beyond the people who voted.

• Off — the entry appears on your changelog quietly. The voters on any post it closes are still emailed. Boost off is not silence.
• On — your changelog subscribers are emailed, and the widget launcher on your site shows a dot until that visitor has read it.

The switch says which it will do, with the number, before you publish.

A boosted entry for one board reaches the people subscribed to your whole changelog plus the people subscribed to that board. A boosted company-wide entry does not reach somebody who subscribed to one product only — they asked about that product, and a company announcement is not that product's release.

Publish now or later

Publish puts it live immediately. Save draft keeps it out of sight with nothing sent.

To schedule it, set a publish date and time and save. It goes out on its own, and the emails go with it — once, even if the scheduler runs twice.

Subscribers

Anyone reading your changelog can press Subscribe. They are asked to prove their address with a six-digit code first, so nobody can be signed up by somebody typing their address in.

Each board's changelog has its own subscribe button, so one person can follow your whole changelog, or one product, or both — they are separate subscriptions.

The Subscribers tab lists them with what each one signed up for, and anyone can unsubscribe from the bottom of any email. That is permanent until they ask again themselves; you cannot add them back.