RocketChat / RocketChat/Rocket.Chat

Status (auto presence) is incorrect in version 7.7.0

Open
#36,159 15 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

Description:

Teammembers that are 100 % offline are shown as Online or AFK.
Same for employees that are working and online. Theire are displayed as AFK an Offline. The Statuses seems to be completely random.

Expected behavior:

The online status of users is shown correctly

  • Offline users are shown as Offline
  • AFK user as Away
  • Users which has set them self to DND are in DND status

-> the status changes correctly if you go offline or online for all other users

Actual behavior:

They randomly displayed as not offline. No one of them is online and not here.
Image

Server Setup Information:
  • Version of Rocket.Chat Server: registry.rocket.chat/rocketchat/rocket.chat:7.7.0
  • License Type: Community
  • Operating System: Ubuntu
  • Deployment Method: docker
  • Number of Running Instances: 1
  • MongoDB Version: 6.0
Client Setup Information
  • Desktop App or Browser Version: Browser Chrome latest and App (Snap Ubuntu) latest
  • Operating System: Ubuntu

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file, test, or entry point is named. Start by reproducing the incorrect presence statuses in the listed Docker, Ubuntu, Chrome, and MongoDB setup, then trace the status update and display flow. Done means offline, away, online, and DND users consistently show the expected status and changes propagate to other users.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
full-stack
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.