Unread state across the inbox
Keep notification counts and unread results telling the same story
Capture the unread badge, active filter, and grouped rows before a read action changes the inbox.
- ✓Badges disagree with unread rows
- ✓Grouping hides read scope
- ✓Unavailable targets interrupt recovery
Notification findings with a counting rule
Count rules made reviewable
Distinguish grouped alerts from individual events before describing an incorrect total.
Consistent read-state criteria
Define which list and badge changes belong to the same action.
Delivery questions kept separate
Keep inbox evidence from becoming an unsupported conclusion about event infrastructure.
Prepare an inbox with different alert states
A notification inbox combines unread counts, grouped events, filters, and links back to the product. In your application, prepare synthetic alerts with a mixture of read and unread items, one grouped event, and a long source title. Capture the global badge, inbox filter, and first visible rows together. Record whether counts are expected to represent groups or individual events. That rule should come from product requirements, not a guess based on the displayed number.
Record the count-changing action
Open the unread filter, mark one group as read, and return from the linked detail page. An example issue is Unread tab shows an empty list while the header still says three unread groups. Show the badge before and after the action and include any pending state. Do not infer a failed delivery or lost event from inconsistent counters. Keep an inaccessible target link separate from the inbox's read-state presentation.
Define a coherent visible result
Upload supported screenshots or recordings to Retick, or capture the browser journey. Inspect AI candidate issues, edit count assumptions, reject claims about delivery systems, and annotate the conflicting unread indicators. Example acceptance criteria: marking a group read updates the relevant list and count consistently; an empty unread view explains its state; and returning from a notification follows the product-approved read behavior. Have the notifications owner confirm whether opening an item marks the entire group or only one event as read.
Follow up on alternate inbox states
After implementation, manually repeat with a single unread item, all items read, and a notification whose target is no longer available. Check long grouped summaries at a narrow viewport and inspect keyboard access to row actions. Verify event generation, ordering, and delivery through your own systems outside Retick. Retick does not operate customer notification channels, monitor event queues, or prove that every alert arrived. Exclude private alert text before capture because redaction is not automatic.
Download accepted findings for a manual file handoff, or export selected issues from the individual media item to an accessible Trello board and list. State the group-count rule and starting filter so developers can distinguish a presentation mismatch from an unresolved question about how events are counted.
Review an inbox read-state change
Show the badge and filtered rows before and after the same action.