Description
In the Permissions section of Rocket.Chat, I think there is an issue where the rendered names of three specific permissions in PermissionRow
were incorrect due to improper translations(en - en) from _id
to display names. This issue led to the following problems:
- Search Functionality: Searching for these permissions required using their
_id
(e.g.,access-setting-permissions
) instead of the rendered name (e.g.,Modify Setting-Based Permissions
). Additionally, spaces were not recognized in the search, and users had to use a-
instead of a space. - Sorting: Sorting of permissions was based on
_id
instead of the displayed names, leading to confusion.
The affected permissions are:
Rendered Name in UI | _id |
---|---|
Change Some Settings | manage-selected-settings |
Modify Setting-Based Permissions | access-setting-permissions |
Bypass rate limit for REST API | api-bypass-rate-limita |
Server Setup Information
- Version of Rocket.Chat Server: 7.2.0
- Operating System: linux
- Deployment Method: cloned
- Number of Running Instances: 1
- DB Replicaset Oplog: enabled
- NodeJS Version: 20.18.0
- MongoDB Version: 7.0.5 / wiredTiger (oplog Enabled)
- Proxy:
- Firewalls involved:
Steps to Reproduce
- Navigate to Administration → Workspace → Permissions.
- Search for
Modify Setting-Based Permissions
:- The search will not find it unless you search (
access-setting-permissions
) which isid
. - Spaces are not recognized; you must use
-
in place of spaces.
- The search will not find it unless you search (
- Observe sorting behavior: Permission names appear sorted based on
_id
rather than their displayed names.
Issue Video:
Additional Information
Sir , Similar kind issues alredy mentioned in old rocket chat version which then removed and not in 7.2.0 version, what i pointed out is few things I think still left to solve,
Sir , I alredy made a PR for it PR #34843 ,
In the PR i get " No Changeset found and PR is missing the ‘stat: QA assured’ label" , I want to know what is the conventions of file name in changeset folder.
I am new to the open-source community, and while I have made every effort to ensure accuracy, I apologize in advance for any mistakes or oversights. I appreciate your understanding and guidance.