RocketChat / RocketChat/Rocket.Chat
Unread counters are inaccurate and no way to reset. Rooms also appear under unread.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
This issue started around the time read receipts were broken (now fixed). The issue was partially fixed in https://github.com/RocketChat/Rocket.Chat/issues/18419
However, this did not fix all counters.
I have attempted to purge rooms to see if the issue would resolve without luck.
Room is empty, shows unread and appears under unread channels.
This issue is impacting users across our rocket instance and lowering the productivity. Not only are the unread counters inaccurate the rooms with bugged counters also appear under unread.
Steps to reproduce:
Purge room or mark all messages read. Unread counter persists.
Expected behavior:
Unread counter is accurate
Actual behavior:
Unread counter is inaccurate
Server Setup Information:
- Version of Rocket.Chat Server: 3.7.0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by reproducing the problem on Rocket.Chat Server 3.7.0 using the purge-room and mark-all-messages-read steps, then trace how unread counters and unread-channel listing are updated. Done means counters reset accurately and empty or fully read rooms no longer appear under unread.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100