-
Notifications
You must be signed in to change notification settings - Fork 10.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[NEW] Subgroups #8873
[NEW] Subgroups #8873
Conversation
This is pretty awesome, thanks for submitting the PR. We'll evaluate and provide feedback as soon as we can. |
This looks awesome. |
A very often requested feature from my users. That is really awesome! @johnmberger |
@johnmberger Nice work !! @core team any idea in which release this will be added ?s |
@johnmberger awesome. And thanks! |
@johnmberger truly awesome! A pledge to @RocketChatAppIn order to make it possible for developers implementing solutions on their own - like @johnmberger and myself, it would be very helpful to at least know your cornerstones: How will the data model look like and are there any defined interfaces already? This would make it possible for us to develop our custom threading workarounds and switch to the "real" threading once it's available. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added some indications for what needs to be defined in order to harmonize different threading implementations on model level
{ | ||
$set: | ||
{ | ||
'subGroup': true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was e. g. interesting to know whether the thread will be a separate room type or remain in the same type as the parent
{ | ||
'subGroup': true, | ||
'subGroupName': room.subGroupName, | ||
'originalRoomId': room.originalRoomId |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
which property shall be used to form the hierarchy - or whether a hierarchy shall exist after all and not only some sort of "tagging"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, it was interesting to know whether the subroom is just a room within a room or whether it is started from a message (which actually made it a thread)
It would be great if these conflicts could be resolved. Having sub channels would be a great benefit. If it is not much work to resolve the issues. it looks like there has already been some work done to get this feature working. |
Is this a dead thread? This function would be great. |
@csimpi - think so unfortunately. Rocket's been going back and forth about message threading for awhile and probably won't merge this in until they make up their mind. |
Aww, it's a same. Nowadays the biggest issue with the productivity team chats is the searching in the history all the time. I don't understand why nobody is willing to implement a solution like this, it would be so much easier If the users would be able to tag their messages if that's necessary. |
@csimpi It isn't a case of people not being willing to implement it, people are willing to implement it. The main dev team for Rocket.Chat are being pushed and pulled in multiple directions by the community as to how this should look and function. Thus, it's likely that the functionality will need to be implemented via a plugin, as they'll never satisfy everybody. IMO, this should be an API endpoint and different ways of rendering it should be viable through plugins, though something should ship out of the box because all the major competitors of Rocket.Chat seem to have this sorted in some form or another. |
Yes, I completely agree, there should be an API for plugins, it would be awesome to solve this in the house :) |
@Sing-Li @brunosquadros this is the top most important feature. It is vital for platform organization and community management. We, and other people we know, have gone through severe complications to have a half-decent, semi-working workaround for this feature. If it were integrated on the most basic level, it wouldn't be a problem to adjust it however one wants. |
As I understand, the function does not work? |
|
Thank you @johnmberger for the hard work on this PR and @mrsimpson for the feedback and deep technical considerations about the underlying data model. We have used this code as the bases for our implementation. The result is the initial implementation added via PR #13541 by @ggazzo We will still use this PR as a reference in the future as we plan to improve the navigation by moving discussion under their parent channels. We will wait for more community input before we move this forward. Thank you again for helping us build such a complex and highly demanded feature. |
I would like to know about Subgroups. |
@RocketChat/core
Introduces subgroups, which are child rooms that can be created from channels or private groups. These subgroups are ideal for conversations that are tangentially related to a parent room. Subgroups can be created via a menu on the flextab bar.
creating a subgroup
![screen shot 2017-11-15 at 11 32 49 am](https://user-images.githubusercontent.com/15810385/32853584-fa57abe2-c9f8-11e7-8f56-a73df86ecc3d.png)
Users have the option of collapsing a parent room's subgroups to reduce clutter on the sidebar.
uncollapsed
![screen shot 2017-11-15 at 11 26 00 am](https://user-images.githubusercontent.com/15810385/32853603-08965c62-c9f9-11e7-8c01-a939a916f5d9.png)
collapsed
![screen shot 2017-11-15 at 11 31 32 am](https://user-images.githubusercontent.com/15810385/32853611-0ecfdd06-c9f9-11e7-9d79-5e162041139c.png)
Users also have the option to have subgroups collapsed by default when they log in.
![screen shot 2017-11-15 at 11 30 52 am](https://user-images.githubusercontent.com/15810385/32853625-1686a58e-c9f9-11e7-9a8a-befa3651b4ab.png)