-
Notifications
You must be signed in to change notification settings - Fork 3
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
Requests without topics - another entry to threading #418
Comments
@janrudolph your feedback, please. |
Technical remarks
|
@mrsimpson I am missing the part of defining the parent room. Do we configure it in the admin backend? By the way, UI design of "ask a question" optional: right sidebar shows a hint that a knowledge base will be present soon |
@mrsimpson Is the implementation of the knowledge base in public and private channels also scope of this issue? |
…tify/Rocket.Chat into #418-requestless-threading
…tify/Rocket.Chat into #418-requestless-threading
Should be resolved by releasing |
…tify/Rocket.Chat into 418-requestless-threading
Replacing #179 based on the last product refinement
Motivation
Currently, requests are the heavy threads based on topics only.
This limits their usage and requires casual users to understand the data model and room types. In order to allow more flexible processes for asking a question (#145, #178), the request must not only be created on the basis of a topic but also on any public or private channel.
Also, people need to join a channel in order to create a thread which is cumbersome for newbies and in some cases unwanted (private groups shall remain privatem, still someone might want to ask a question for it) .
Purpose
As a user who wants to ask something, I want to start a question/request/thread for any room without joining the room in order to get help from those experts.
Threads are a common feature across multiple chat platforms and mostly accepted by users. There's a loooooong ungoing discussion RocketChat#1112 how to implement threads in RC.
This issue is about enabling threading without the need to use the fullblown request/topics mechanism.
Tasks
createRequest
template can pretty much be copied. However, it should only contain one single input for the initial message.c
orp
Remarks
parentRoomId
and optionally aoriginMessageId
.The text was updated successfully, but these errors were encountered: