Feature Request: Unread Count for Threads within Messages

[muhammedogz]

Motivation
In our project, we employ the getstream chat where every message can have threads. For our users, it's important to treat each thread as separate messages to accurately track and manage unread messages. Currently, there is no straightforward way to get an unread count of threads in messages. This is a problem because it makes it difficult for users to identify which threads contain unread messages and subsequently navigate to them. This can lead to missed conversations and information, creating frustration among users.

Proposed solution
We propose the addition of a feature that would allow us to retrieve an unread count of threads in messages in the getstream chat, similar to how we can get an unread count of messages in a channel. This would ideally be implemented as a function or a field that we could easily access via the API, updating in real time as messages are read or new messages are received in the threads.

Acceptance Criteria
The function/feature accurately counts the number of unread threads within messages for any given user and is easily retrievable.

Also, it seems relative with this issue: GetStream/stream-chat-flutter#1337

[MartinCupela]

Hello @muhammedogz, thank you for the proposal. Unread counts in threads are indeed on our roadmap. At the moment I cannot provide you with exacte ETA.

[AndreHaueisen]

Any updates on this issue?

[borisdaenen]

Same question here. Is there a way to get an unread_count for threads or can we include the unread replies in the channel's unread_count?

[MartinCupela]

We are working on update that will introduce threads with unread counts. The PR draft is available here: #2407

[borisdaenen]

That’s great news! Thank you

…

On 3 Jun 2024 at 13:10 +0200, MartinCupela ***@***.***>, wrote: We are working on update that will introduce threads with unread counts. The PR draft is available here: #2407 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>

[stream-ci-bot]

🎉 This issue has been resolved in version 12.0.0-rc.15 🎉

The release is available on:

• GitHub release
• npm package (@rc dist-tag)

Your semantic-release bot 📦🚀

[stream-ci-bot]

🎉 This issue has been resolved in version 12.0.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀