Labels on changelog entries look like a detail. They're actually most of how people read a changelog: they skim the labels, and only stop on the entries that matter to them.
Start with three
New, Improved and Fixed cover almost everything:
- New is something you couldn't do before.
- Improved is something you could do, now better.
- Fixed is something that was broken and isn't anymore.
These three answer the question every reader has: is this something I should try, something I should notice, or something I can stop working around?
When you need a fourth
Add a label when there's a group of readers who want to find a particular kind of change and can't. Some that earn their place:
- Security, for changes admins need to know about even if users don't.
- API, if developers read your changelog for changes that affect their code.
- Removed, for the rare times you take something away. People should never discover a removal by accident.
Each of these has a reader who'll look for it specifically. That's the test.
When you have too many
You know you've gone too far when entries carry three labels each, or when labels describe your team's structure: "Frontend", "Platform", "Mobile squad". Readers don't care which team built it. They care what changed for them.
A long label list also gets applied inconsistently. One person tags a change Improved, another tags a similar one Enhancement, and the filter stops meaning anything.
Write labels in the reader's words
"Fixed" is better than "Bug fix". "New" is better than "Feature". Short words, as a customer would say them. And if your customers read in other languages, labels are your own words, so name them however your readers talk.
Use them in the email too
When a release is emailed to the people who asked for it, the label is the first thing they see. "New: export any board to CSV" gets opened. Make sure the label is the right one.
A changelog is a promise that you'll tell people what changed. Labels are how you keep that promise for readers who only have thirty seconds.