RocketChat / RocketChat/Rocket.Chat

Status message doesn't change once a custom status is set

Open
#21,245 0 comments 0 reactions 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:

When a user sets custom status and then changes it afterwards to one of the presets "busy", "away", "invisible" or "online", the status message doesn't change according to the preset values instead stays set to the custom message.

Steps to reproduce:
  1. Click on the user avatar on top left.
  2. select a custom status and create a custom status.
  3. Change the status back to anyone of the four presets.
Expected behavior:

The status should change according to the presets once the user switches it.

Actual behavior:

Status doesn't change once a custom status is set, irrespective of what preset user clicks
https://user-images.githubusercontent.com/70897225/111989208-7bb73b00-8b37-11eb-8a79-08b2e2eba4cd.mov

Server Setup Information:
  • Version of Rocket.Chat Server: 3.13.0
  • Operating System:
  • Deployment Method:
  • Number of Running Instances:
  • DB Replicaset Oplog:
  • NodeJS Version:
  • MongoDB Version:
Client Setup Information
  • Desktop App or Browser Version:
  • Operating System:MacOS 10.15.7 Catalina
Additional context
Relevant logs:

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

Start by reproducing the issue through the user avatar menu: create a custom status, then select each of the busy, away, invisible, and online presets. Trace the status and status-message handling from that UI flow. Done means each preset replaces the custom message with its expected preset value.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.