RocketChat / RocketChat/Rocket.Chat

Regular members listed as owners in channel members list

Open
#37,370 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Description:

The members on channel list are mentioned under Owners moniker when they are just users, and vice versa.

Actual roles work ok, so this is a cosmetic but confusing error in the channel members list.

This has been around for at least since RC 7.8.x when we noticed it, but I hadn't just reported it earlier.
We don't know what triggers this issue.

Steps to reproduce:
  1. (Not known what triggers this issue)
  2. Go to channel where you are an owner
  3. Check the members list, pay attention to your mentioned status in it, and check your members management menu
Expected behavior:

Owners are sorted correctly as owners in the members list.

Actual behavior:

Real owner is marked as a regular member. Random regular member is shown as an owner.

These "fake owners" do not have real ownership options in their menus either, nor do they have badge in their messages.

The real owner has an option to remove and promote owners as usual. The real owner Toni Härkönen (in the picture) checking the menu on himself.

Image
Server Setup Information:
  • Version of Rocket.Chat Server: 7.12.0
  • License Type: Enterprise
  • Number of Users: 500+
  • Operating System: RHEL8
  • Deployment Method: docker
  • Number of Running Instances: 4
  • DB Replicaset Oplog: Yes
  • NodeJS Version: v22.16.0
  • MongoDB Version: 7.0
Client Setup Information
  • Desktop App or Browser Version: Latest Chrome or Firefox
Additional context

Promoting members as owners or demoting owners back to members on the channel temporarily fixes the members view issue. But refreshing the RC window breaks the sorting again.

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 or test is identified. Start by reproducing the issue in a channel's members list, comparing owner and regular-member roles before and after refreshing the Rocket.Chat window; done means the displayed owner labels remain correct and match the available management options.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.