RocketChat / RocketChat/Rocket.Chat

Registration of the workspace is unskippable in version 6.5

Open
#31,163 44 comments 20 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

Hello,

I've had an instance of Rocket.Chat running for three years now, and I've never had the need (let alone the desire) to register it as I don't use push notification nor store addons or anything that are limited to subscribed users.

After upgrading to version 6.5, the admin account get the modal below, without the ability to skip this step or the continue the wizard without registering.

This issue is similar to #31157 but I want to focus on the fact that there should be a way to skip the registration.
This would also be needed for instances in test environments.

image

Server Setup Information:
  • Version of Rocket.Chat Server: 6.5
  • Operating System: Ubuntu 20.04
  • Deployment Method: snap
  • Number of Running Instances: 1

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 admin setup wizard on Rocket.Chat 6.5 and inspect the registration step shown in the issue. Trace how the wizard proceeds after registration and identify the existing path for test or unregistered instances. Done means an administrator can skip workspace registration and continue the wizard without registering the instance.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 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.