Contradictions in the rights to archive room

Open
#27,793 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

No source files or tests are named. Start by reproducing the room-owner permissions on the reported server versions and trace the archive and unarchive permission checks. Done means a room owner who can archive a room can also unarchive it by default, without manually assigned rights.

Written by the indexing model from the issue text.

Description

Description:

By default, the owner of the room has rights to archive, but not to unarchive.

Expected behavior:

If there are rights for archiving, there should be also for unarchiving.

Actual behavior:

By default, the owner of the room does not have the rights to unarchive the room. You have to assign them manually.
image

Server Setup Information:

Tested on server versions 4, 5 and 6.

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

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.

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.