Converted team stays under Teams and still offers “Convert to channel”

Open
  • Is something wrong?
#43,536 4 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

@AlokUnscripted is already working on this.

Since Nov 6, 2026.

  • #43566 by @AlokUnscripted — open

Assessment

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

Research direction

Start by reproducing the conversion with a private team and tracing the sidebar and Team info state after the room history confirms conversion. Compare the immediate view with the state after refreshing and reopening the room; the issue does not name files or tests. Done when the room moves under Channels and shows Channel info immediately, without offering Convert to channel again.

Written by the indexing model from the issue text.

Description

type: bug
Image Image

I reproduced this with two private teams in my local workspace. After conversion, the room history says the team was converted to a channel, but the sidebar still lists it under Teams and the right panel still shows Team info.

Steps to reproduce

  1. Create a private team and open Team info.
  2. Select Convert to channel → Continue → Convert.
  3. Once the conversion appears in the room history, check the sidebar and reopen the menu in Team info.
    Expected: The room moves under Channels and the panel shows Channel info immediately.

Actual: The room remains under Teams and the menu still offers Convert to channel. On my first test, selecting it again returned team-does-not-exist. On my second test, I went Home, refreshed, and reopened the room. It then appeared under Channels with the correct menu.

Environment: Local Rocket.Chat at commit 2a1da3434b, started with yarn dsv, Chrome on macOS.

I noticed this while investigating #43288. I’d like to investigate why the sidebar and room controls still show the team state after conversion.

Dominant language
TypeScript
Stars
46.5k
Forks
14.1k
Avg merge
1d 21h
Merged PRs (30d)
381

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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.

More from RocketChat/Rocket.Chat

All issues in RocketChat/Rocket.Chat

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.