Skip to content
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

streams api: Allow setting muted/pinned for other users (for support streams) #9479

Open
showell opened this issue May 21, 2018 · 2 comments

Comments

@showell
Copy link
Contributor

showell commented May 21, 2018

See discussion here:

https://chat.zulip.org/#narrow/stream/127-integrations/subject/Mute.20channel/near/583514

For organizations doing support, it can make sense to auto-subscribe users to certain "support streams" in the API, and you may often want the streams to be pinned and muted by default. (Pin them so the users are aware of them, but mute them to avoid spam.)

We currently don't allow muting/pinning on behalf of users, so this would necessitate some backend changes, and we almost certainly want to restrict this to either subscription time and/or to people with stream-owner powers.

If this feature becomes popular, we would probably make it be part of the UI as well.

@zulipbot
Copy link
Member

Hello @zulip/server-streams members, this issue was labeled with the "area: stream settings" label, so you may want to check it out!

@showell
Copy link
Contributor Author

showell commented May 21, 2018

A closely related idea here is to make descriptions be pinned to the top of message streams, so for support streams you could suggest to users that they do things like mute/pin the streams (as well as explaining or linking to the protocols for how to ask good questions, etc.). Of course, if you don't pin a stream right away, there's the problem the users won't even know the stream exists. The original message to the stream sort of mitigates that, but maybe not enough.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants