Skip to content

Permanent stuck unread-notification when starting a thread with a reply message #23976

@quazgar

Description

@quazgar

Steps to reproduce

  1. Have threads enabled
  2. Person A: write message "text A"
  3. Person B: Reply to A without threads
  4. Person A: Reply in thread to B

Outcome

What did you expect?

Reading the message should mark it as read.

What happened instead?

  1. Person B's message will permanently be marked as unread and highlighted (because it's a reply) in A's app.
  2. The thread does not show up as unread in the thread overview
  3. 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

No one assigned

    Labels

    A-NotificationsA-ThreadsO-OccasionalAffects or can be seen by some users regularly or most users rarelyS-MajorSeverely degrades major functionality or product features, with no satisfactory workaroundT-DefectX-Cannot-ReproduceX-Needs-InfoThis issue is blocked awaiting information from the reporter

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions