You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A lot of users ask for ability to manage their chats (DMs, private groups,channels and discussions) with user defined groups like by project, status (active, hold, finished) or by department (HR, Accounts, Chiefs) or any other groups user want.
Steps to reproduce:
Go to chat list
All chats in one list
You can group chats by type, but users want their own groups
Expected behavior:
Users should have ability to create chat groups and move their chats to that groups
Actual behavior:
There is only chat type grouping, which not enough for users to manage their chats
Server Setup Information:
Version of Rocket.Chat Server: 3.6.0
Operating System: CentOS7
Deployment Method: docker
Number of Running Instances: 25
DB Replicaset Oplog: Enabled
NodeJS Version: 12.16.1
MongoDB Version: 4.0.17
Client Setup Information
Desktop App or Browser Version: 2.17.11
Operating System: Windows 10
Additional context
No additional context
Relevant logs:
No logs
The text was updated successfully, but these errors were encountered:
Here is a proposal for introducing teams RocketChat/Rocket.Chat#658 (comment) which is also related to grouping of users in RocketChat/Rocket.Chat#7152 .
Description:
A lot of users ask for ability to manage their chats (DMs, private groups,channels and discussions) with user defined groups like by project, status (active, hold, finished) or by department (HR, Accounts, Chiefs) or any other groups user want.
Steps to reproduce:
Expected behavior:
Users should have ability to create chat groups and move their chats to that groups
Actual behavior:
There is only chat type grouping, which not enough for users to manage their chats
Server Setup Information:
Client Setup Information
Additional context
No additional context
Relevant logs:
No logs
The text was updated successfully, but these errors were encountered: