Template
Changelog page template
A changelog page template: draft, label and publish release notes in Looph, and tell the voters of linked requests when their feature ships.
Teams that want shipped work to automatically close the loop with the customers who asked for it.
- Entry states
- 2
- Entry types
- 3
- Parts of an entry
- 5
- Setup steps
- 6
Use this template
Copy the setup
Copy the checklist below into your setup notes and follow it in Looph. Changelog entries are written in the app, so there is no file to import.
Setup checklist
Changelog page template (looph.ing/templates/changelog) Entry states: - Keep "Draft" - Keep "Published" These are the two states of a changelog entry, not post statuses. Linked posts move to Complete, under whatever name your workspace gives it, only if you choose that when publishing. Entry types: - New - Improved - Fixed Each entry needs: - Title - Summary - Linked posts - Type - Share image Setup steps: 1. Open the changelog and write your first entry as a draft. Pick a type and lead with what changed for the reader. 2. Link the posts the release resolves before publishing. Those links are what let you notify voters and move the posts to Complete. 3. Publish, and in the dialog choose whether to mark linked posts Complete, tell the people who asked, and comment on each post. 4. Review notification settings. Each person chooses which emails they get, and the same status announced twice within 24 hours sends only one email. 5. Subscribe a Slack channel to published changelog entries, so each release also lands where your team reads. 6. Optionally serve the changelog on your own subdomain, so its pages build search visibility for your brand.
Templates aren't applied automatically yet: you set the board up yourself by following the steps on this page. One-click templates are coming soon.
Fit
When to use this template
A good fit when
You ship regularly, and the people who asked for things never find out. A changelog in the same tool as your board fixes that: link an entry to the requests it resolves and you can tell their voters when you publish, with no follow-up list to maintain.
It also gives customers, prospects and search engines a dated public record of what you have shipped, with an RSS feed and a read-only embed for your own site.
Pick something else when
It is the wrong place for engineering release notes full of ticket numbers and migration steps. Keep those next to your code and write the changelog for the person who asked.
If you release once or twice a year, a blog post per release may serve you better than a changelog page that looks abandoned between entries.
What's inside
Entry states, types and contents, and why each one is there
A changelog entry is a draft until you publish it. Below are the states, the types readers filter by, and what each entry needs.
Entry states
- Draft
- Where an entry is written and reviewed. Nothing is sent and readers see nothing while it sits here, so link the posts it resolves before you publish.
- Published
- Publishing is the step that matters. The publish dialog lets you mark the linked posts Complete, tell everyone who voted on or followed them that it shipped, and add a comment to each post. Treat it as a send button.
These are the two states of a changelog entry, not post statuses. Linked posts move to Complete, under whatever name your workspace gives it, only if you choose that when publishing.
What each entry needs
- Title
- Name the change in the reader's words, such as "Export any report to CSV", rather than the internal epic or ticket name.
- Summary
- Lead with what changed and who it affects. Two clear sentences beat a bulleted list of tickets.
- Linked posts
- The posts this release resolves. Linking is optional, but it is what lets you tell their voters and followers on publish, so link wherever a request exists.
- Type
- New, Improved or Fixed, so readers who only care about fixes can filter to them.
- Share image
- Shown when the entry is shared in chat or on social media, which is where many readers will first see it.
Entry types
- New
- Improved
- Fixed
New, Improved and Fixed are the changelog's entry types, and readers can filter the public page by them. Each entry can also carry a free-text category. Three types cover almost every release.
Setup
Set it up in Looph
Each step in order, with the guide that covers it.
- 01
Open the changelog and write your first entry as a draft. Pick a type and lead with what changed for the reader.
- 02
Link the posts the release resolves before publishing. Those links are what let you notify voters and move the posts to Complete.
- 03
Publish, and in the dialog choose whether to mark linked posts Complete, tell the people who asked, and comment on each post.
- 04
Review notification settings. Each person chooses which emails they get, and the same status announced twice within 24 hours sends only one email.
- 05
Subscribe a Slack channel to published changelog entries, so each release also lands where your team reads.
Setup: Slack integration
- 06
Optionally serve the changelog on your own subdomain, so its pages build search visibility for your brand.
Illustrative examples
Example posts
Made-up posts that show what a useful entry on this board looks like. They are not from real customers.
Example · New
Export any report to CSV
Every report now has an Export button that downloads the filtered view as a CSV file. Linked to the two feature requests that asked for it.
Published
Example · Improved
Dashboards load faster in large workspaces
Workspaces with many projects now load the dashboard in a fraction of the previous time. Nothing to change on your side.
Published
Example · Fixed
Password reset links no longer expire early
Reset links now stay valid for their full window. Linked to the bug report, so everyone who voted on it can be told when this is published.
Draft
Plan
Which plan it needs
Works on Free. The changelog is included on every plan, Free among them, as are voter notifications on status change and the Slack integration. A custom domain and removing Looph branding need Growth. Compare plans.
How the pieces work: Changelog. Teams running this workflow: Customer feedback management for SaaS product teams and Feature voting and roadmaps for mobile app teams.
More templates
Other starting points
Customer feedback portal template
B2B teams and agencies that want a single branded destination per account instead of scattered email threads.Public product roadmap template
Any team that wants to publicly show what's coming next and reduce 'is this being worked on?' questions.Beta feedback board template
Teams running a private or invite-only beta that need structured, votable feedback before a general release.Internal IT request board template
Internal IT and operations teams that need a searchable, votable alternative to a ticketing spreadsheet.
Related
The features and reading behind this template
Start collecting feedback in five minutes
Free forever on one board, with unlimited members and a 14-day Business trial. No credit card, no sales call.
Unlimited members · Published prices · Cancel anytime