Skip to content

unread notifications in threads ineffective/difficult to use. #26726

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
syadnom opened this issue Dec 11, 2023 · 7 comments
Closed

unread notifications in threads ineffective/difficult to use. #26726

syadnom opened this issue Dec 11, 2023 · 7 comments
Labels
T-Defect X-Needs-Info This issue is blocked awaiting information from the reporter

Comments

@syadnom
Copy link

syadnom commented Dec 11, 2023

Steps to reproduce

essentially background task, do nothing to reproduce except wait around for people to chat in threads. Client shows unread messages indicator but cannot find unread messages in client anywhere.

Outcome

Some method to jump to unread threads easily. It's very difficult to follow along on threaded conversations when the unread notifications are non-functional

Operating system

macos, windows

Application version

always current to date of post

How did you install the app?

download from matrix.org featured clients

Homeserver

No response

Will you send logs?

Yes

@t3chguy t3chguy transferred this issue from element-hq/element-desktop Dec 12, 2023
@t3chguy
Copy link
Member

t3chguy commented Dec 12, 2023

Application version
always current to date of post

Not helpful, please fill it

Will you send logs?
Yes

Not seeing any logs from you

@t3chguy t3chguy added the X-Needs-Info This issue is blocked awaiting information from the reporter label Dec 12, 2023
@ronnyaa
Copy link

ronnyaa commented Jan 16, 2024

was going to submit the same issue. but probably better to just comment here.
It is very hard to find the right thread with the unread message. you have to scroll for days to find the small dot.

perhaps an addition to the top right dropdown that today contain "All threads" and "My threads" to also have the entry "unread threads"

Element version: 1.11.51
Crypto version: Olm 3.2.15

I can send logs if any are requested but the feature request is self evident in any larger room with many active threads.

@syadnom
Copy link
Author

syadnom commented Jan 16, 2024

we're considering moving off the platform for the poor thread and notification handling. It's kills conversations off.

@dimm0
Copy link

dimm0 commented Jan 17, 2024

Same here. Old threads are randomly becoming unread, need to scroll for tens of threads to find one. The global channel "Mark as read" sometimes doesn't work (sometimes works), but after that new threads are becoming unread.

@ronnyaa
Copy link

ronnyaa commented Jan 22, 2024

tens ? i have some hundreds, and it takes an hour to scroll thru them all to hunt the small white dot's that are scattered around. 99% of them are just old threads with nothing new in them.

It seems to be a bigger issue in rooms with bridges. but the request is mostly about how to deal with it when it have happened, then to stop it from happening. hence a filter to show only threads with unread, or a way to mark all threads as read. or preferably both :)

what kind of info is needed ?

@t3chguy
Copy link
Member

t3chguy commented Apr 24, 2024

Closing due to lack of response on the 2 prompts

@t3chguy t3chguy closed this as not planned Won't fix, can't repro, duplicate, stale Apr 24, 2024
@ronnyaa
Copy link

ronnyaa commented Apr 24, 2024

It was not my original issue. but i can provide info if that is needed.

not sure what logs are needed on a feature request. but the element version i use is
Element version: 1.11.65
Crypto version: Olm 3.2.15

Basically any method to find the threads with unread messages in them.
image

on the top dropdown a "unread threads" would work.

a bonus would be a "mark all threads read" to mark all as read on this matrix room.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-Defect X-Needs-Info This issue is blocked awaiting information from the reporter
Projects
None yet
Development

No branches or pull requests

4 participants