Moving topics between streams #6427
Comments
|
This seems like a valuable feature to me :) Would you be willing to discuss implementing this more in detail with us on https://chat.zulip.org? |
|
Hello @zulip/server-misc members, this issue was labeled with the area: topics label, so you may want to check it out! |
|
Linking to the thread here: |
|
any updates? |
|
Semi-related: it would be great to be able to move a range of messages between topics, e.g. copying/moving messages from from a private message thread into a public topic is something we find ourselves doing frequently at our company. Copy-paste doesn't preserve formatting, and copy pasting each message's raw text is too labor intensive when it's often ~20-100 messages. CC: @cowpig |
|
I'd add that the ability to copy the raw markdown for a range of messages would probably be enough to handle most of our needs, if that's simpler to implement. |
|
any updates? :-) |
|
This is a must for the way Zulip works 👍 |
|
So, I don't have an update on this other than it's something we'll be looking to pick up after the 2.1 release. One important thing that we have done in this direction is adding markdown syntax for mentioning a topic, which will likely be used as part of communicating clearly what happened with this sort of thing. |
|
Vote +1 for moving topics to a different stream. |
|
We also need this feature :) It would be great to have it. |
|
@zulipbot claim |
|
Hello @dobleuber! Thanks for your interest in Zulip! You have attempted to claim an issue without the labels "help wanted", "good first issue". Since you're a new contributor, you can only claim and submit pull requests for issues with the help wanted or good first issue labels. If this is your first time here, we recommend reading our guide for new contributors before getting started. |
This commit reuses the existing infrastructure for moving a topic within a stream to add support for moving topics from one stream to another. Split from the original full-feature commit so that we can merge just the backend, which is finished, at this time. This is a large part of #6427. The feature is incomplete, in that we don't have real-time update of the frontend to handle the event, documentation, etc., but this commit is a good mergable checkpoint that we can do further work on top of. We also still ideally would have a test_events test for the backend, but I'm willing to leave that for follow-up work. This appears to have switched to tabbott as the author during commit squashing sometime ago, but this commit is certainly: Co-Authored-By: Wbert Adrián Castro Vera <wbertc@gmail.com>
This is part of #6427, adding support for live-updating the Zulip UI to move messages to a new topic. As noted in the comments, there is still a bug to be fixed here involving guest users, but the overall implementation is pretty well tested manually (which is how we test most message-edit UI work since there's so much complexity involved). Co-Authored-By: Wbert Adrián Castro Vera <wbertc@gmail.com>
|
This feature is 2/3 merged at this point; I've opened #14499 to track something that I'd love feedback on from some of the many folks excited about this feature: what set of options organization administrators should be able to select from for who gets to move blocks of messages between streams. That'll probably also be a good place to discuss other UI feedback details like whether the person moving the messages has control over whether the "tombstone" messages communicating that the messages were moved get sent, and perhaps details on whether those messages should be marked as automatically read for the person doing the move. |
This commit reuses the existing infrastructure for moving a topic within a stream to add support for moving topics from one stream to another. Split from the original full-feature commit so that we can merge just the backend, which is finished, at this time. This is a large part of zulip#6427. The feature is incomplete, in that we don't have real-time update of the frontend to handle the event, documentation, etc., but this commit is a good mergable checkpoint that we can do further work on top of. We also still ideally would have a test_events test for the backend, but I'm willing to leave that for follow-up work. This appears to have switched to tabbott as the author during commit squashing sometime ago, but this commit is certainly: Co-Authored-By: Wbert Adrián Castro Vera <wbertc@gmail.com>
This is part of zulip#6427, adding support for live-updating the Zulip UI to move messages to a new topic. As noted in the comments, there is still a bug to be fixed here involving guest users, but the overall implementation is pretty well tested manually (which is how we test most message-edit UI work since there's so much complexity involved). Co-Authored-By: Wbert Adrián Castro Vera <wbertc@gmail.com>
This commit reuses the existing infrastructure for moving a topic within a stream to add support for moving topics from one stream to another. Split from the original full-feature commit so that we can merge just the backend, which is finished, at this time. This is a large part of zulip#6427. The feature is incomplete, in that we don't have real-time update of the frontend to handle the event, documentation, etc., but this commit is a good mergable checkpoint that we can do further work on top of. We also still ideally would have a test_events test for the backend, but I'm willing to leave that for follow-up work. This appears to have switched to tabbott as the author during commit squashing sometime ago, but this commit is certainly: Co-Authored-By: Wbert Adrián Castro Vera <wbertc@gmail.com>
This is part of zulip#6427, adding support for live-updating the Zulip UI to move messages to a new topic. As noted in the comments, there is still a bug to be fixed here involving guest users, but the overall implementation is pretty well tested manually (which is how we test most message-edit UI work since there's so much complexity involved). Co-Authored-By: Wbert Adrián Castro Vera <wbertc@gmail.com>
This completes the implementation of support for moving a topic to another stream by adding a basic UI for it. Fixes zulip#6427, which was previously the most-upvoted issue request in Zulip. There are likely to be a bunch of follow-up UI improvements on top of this change to fully flesh out the feature.
This commit reuses the existing infrastructure for moving a topic within a stream to add support for moving topics from one stream to another. Split from the original full-feature commit so that we can merge just the backend, which is finished, at this time. This is a large part of zulip#6427. The feature is incomplete, in that we don't have real-time update of the frontend to handle the event, documentation, etc., but this commit is a good mergable checkpoint that we can do further work on top of. We also still ideally would have a test_events test for the backend, but I'm willing to leave that for follow-up work. This appears to have switched to tabbott as the author during commit squashing sometime ago, but this commit is certainly: Co-Authored-By: Wbert Adrián Castro Vera <wbertc@gmail.com>
This is part of zulip#6427, adding support for live-updating the Zulip UI to move messages to a new topic. As noted in the comments, there is still a bug to be fixed here involving guest users, but the overall implementation is pretty well tested manually (which is how we test most message-edit UI work since there's so much complexity involved). Co-Authored-By: Wbert Adrián Castro Vera <wbertc@gmail.com>
This completes the implementation of support for moving a topic to another stream by adding a basic UI for it. Fixes zulip#6427, which was previously the most-upvoted issue request in Zulip. There are likely to be a bunch of follow-up UI improvements on top of this change to fully flesh out the feature.
There are often circumstances in our (@recursecenter's) Zulip realm where it would be very useful to be able to move a topic to a different stream. In particular, with over 1000 people in our realm, and onboarding ~30 new users every 6 weeks, it's difficult to keep everyone on the same page about what's on topic for discussion in which stream. Often a valuable discussion will start, but in the wrong stream. This is an especially bad situation for us because we have a lot of relatively infrequent users who, when they come back, want to catch up on only the discussion that's interesting to them. Having off-topic discussions makes it harder for them to do this by subscribing to just the streams they're interested in (by diluting the discussion in said streams).
We've always tried to moderate "by hand" in this circumstance, by just asking the people involved to move the discussion to a different stream. What we've observed, however, is that this often has the effect of killing the discussion, since the people involved feel like they've "done something wrong", and there's a fair amount of inertia to creating a new topic, moving everyone over, etc.
What we would like is a way to move topics to a different stream. The UI I imagine for this is something like another button next to the "edit name" and "mute" buttons for streams, which, when clicked on, brings up on menu of all the other streams, and then I can select one and the topic will be in that stream instead of the one it's in currently.
Is this a feature Zulip would be interested in having? I'm definitely willing to work on it if so! Apologies if there's already an open issue for something like this; I searched and couldn't find anything.
The text was updated successfully, but these errors were encountered: