-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Closed
Closed
Copy link
Labels
A-NotificationsA-ThreadsO-OccasionalAffects or can be seen by some users regularly or most users rarelyAffects or can be seen by some users regularly or most users rarelyS-MajorSeverely degrades major functionality or product features, with no satisfactory workaroundSeverely degrades major functionality or product features, with no satisfactory workaroundT-DefectX-Cannot-ReproduceX-Needs-InfoThis issue is blocked awaiting information from the reporterThis issue is blocked awaiting information from the reporter
Description
Steps to reproduce
- Have threads enabled
- Person A: write message "text A"
- Person B: Reply to A without threads
- Person A: Reply in thread to B
Outcome
What did you expect?
Reading the message should mark it as read.
What happened instead?
- Person B's message will permanently be marked as unread and highlighted (because it's a reply) in A's app.
- The thread does not show up as unread in the thread overview
- Workaround: Deleting B's initial message by A will remove the notification.
Operating system
Debian Bullseye
Application version
Element version: 1.11.16 Olm version: 3.2.12
How did you install the app?
From https://packages.riot.im/debian
Homeserver
No response
Will you send logs?
No
Metadata
Metadata
Assignees
Labels
A-NotificationsA-ThreadsO-OccasionalAffects or can be seen by some users regularly or most users rarelyAffects or can be seen by some users regularly or most users rarelyS-MajorSeverely degrades major functionality or product features, with no satisfactory workaroundSeverely degrades major functionality or product features, with no satisfactory workaroundT-DefectX-Cannot-ReproduceX-Needs-InfoThis issue is blocked awaiting information from the reporterThis issue is blocked awaiting information from the reporter