Marking Updates as Read
How unread changelog updates are cleared from the page, the badge popup, and the What's New popup.
Unread changelog entries all come from the same release list, but Work Planner gives you a few different ways to clear them. The most useful part to understand is that each changelog surface behaves slightly differently.
From The Changelog Page
On the full Changelog page, unread entries show a Mark as read button on the release card itself. Clicking that button clears only that one release. The app then refreshes the unread count in the header so the badge immediately reflects the change.
From The Changelog Badge Popup
The badge popup also lets you clear entries one at a time. That makes it useful when you want to keep later releases unread for now, but you no longer want the oldest item counted.
From The What's New Popup
The What's New popup is the batch-clear option. If you dismiss it while unread items are showing, Work Planner treats that as you having seen the list and marks every unread item in that popup as read.
Why The Count Changes
- Single entry cleared: the number usually drops by one because one release changed from unread to read.
- Batch cleared from the popup: the number can drop by several at once because the popup clears every unread item it was showing.
- Already read entries: clearing something that is already read does not reduce the number again.
When To Use Each Method
- Use the page: when you want to read each update properly and clear them selectively.
- Use the badge popup: when you just want a quick manual check from the header.
- Use the What's New popup: when you are happy to clear the current unread batch in one go.
Related articles
- Changelog Page: the full release history with per-entry read controls.
- Changelog Badge: the manual popup launched from the header.
- What's New Popup: the automatic popup that clears unread items on dismiss.