Discussion resolution in context
Show what resolving a comment thread changes on screen
Keep thread identity, active filters, and selection changes visible as discussions are resolved and reopened.
- ✓Counts carry over to another thread
- ✓Filters make resolution look like deletion
- ✓Selection after resolution is undefined
Thread reports with filters and anchors intact
Filter-aware thread evidence
Explain why a discussion leaves the list before reporting it as missing.
Selection behavior with an owner
Make the next selected thread a deliberate collaboration design decision.
Thread-specific acceptance
Require author and reply counts to match the discussion currently in view.
Start with identifiable discussion context
Resolving a thread can remove it from a filtered view while leaving an anchor elsewhere in the interface. In your product, create harmless comments attached to two distinct sections and one already resolved thread. Capture the open-thread filter, the selected anchor, and the thread actions before making changes. Record the account role and intended resolve permissions. Use synthetic names and text so the review does not expose private conversations or confidential document content.
Follow resolution into the remaining list
Record resolving the selected thread, opening the next visible thread, and switching the filter to include resolved discussions. An example issue is Next thread shows the resolved thread's reply count after the list collapses. Include the anchor labels and count before and after resolution. Keep the stale count separate from whether the thread should disappear under the active filter. A missing thread in an open-only view is not automatically evidence of deleted discussion.
Define the filtered-view contract
Capture with Retick or upload supported screenshots and recordings. Review AI candidate issues, edit inferred deletion claims, reject assumptions about notifications, and annotate the mismatched count. Example acceptance criteria: resolving updates the active filter's list consistently; selecting the next thread shows its own author and reply count; and reopening from the resolved view restores the product-approved open state. Have the collaboration owner decide which thread receives selection after resolution so the report does not invent a navigation rule.
Recheck sparse and crowded discussions
After implementation, manually repeat with the only open thread, several nearby anchors, and a role that cannot resolve comments. Inspect long replies and collapsed thread previews. Verify concurrent edits, notification delivery, and durable discussion state through your application's tests and operational tools. Retick does not resolve customer discussions, synchronize collaborators, or verify message delivery. Remove sensitive comment text before capture rather than relying on automatic redaction of uploaded media.
Download the approved findings as a file handoff, or export selected issues from the individual media item to a connected Trello board and list. Include the starting filter and selected anchor so engineering can reproduce the transition instead of treating the stale count as an isolated display typo.
Review a thread resolution sequence
Capture the selected discussion and the list that remains after resolving it.