Show related changes together so customers can browse one release at a time. For example, three separate posts about exports, charts and filters can appear under Version 2.4.1.
Use Version for a version number such as 2.4.1. Use Release for a name such as Spring release. These are labels you enter; filling them in does not publish the post or send an email.
| Group by | What customers see |
|---|---|
| No grouping | Posts without release, version or month headings |
| Month | Posts grouped by their latest status-change month |
| Version | Posts with the same version under one heading |
| Release | Posts with the same release name under one heading |
When grouping by Version or Release, posts without that value are left out of the customer view. Admins can still see them under No version or No release. Fill in the missing value if an update should appear in that view.
Turn on Split large groups by category to show categories inside a group with ten or more posts. ProductLift uses each post's first category. Posts without a category appear under Other.
For example, a large release can contain separate lists for improvements and fixes. Turn this setting off if you want one list under each release heading.
In the timeline view, use the edit control beside a group heading to add Intro text. For version and release groups, you can also set a Custom title. Month headings keep their month name.
Use the introduction to summarize the release, then let each post explain its own change. You can use the AI option to draft the introduction and review it before saving.
Grouping does not combine votes, comments or notification audiences. To write one announcement for several roadmap items, link them to a single release note.