RocketChat/Rocket.Chat

Settings for confirmation for using @all notification on messages

Open

#909 opened on Sep 26, 2015

View on GitHub
 (22 comments) (1 reaction) (0 assignees)TypeScript (13,573 forks)batch import
area: ui/uxgood first issuegsoc-projecttriagedtype: improvement

Repository metrics

Stars
 (45,311 stars)
PR merge metrics
 (Avg merge 6d 1h) (230 merged PRs in 30d)

Description

Even though we had a few funny times when someone shoot an @all notification in the middle at the night on the Demo Server, what do you folks think about the idea of adding a settings-based confirmation before using it?

screen shot 2015-01-30 at 3 36 44 pm

Maybe it could be related to rules such as the number of users in the channel and/or number of different timezones etc.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Contributor guide

Research direction
Examine the current @all notification implementation and settings system. Add a new setting to require confirmation before sending @all messages. Consider integrating with existing notification settings and user preferences.
Tech stack
typescriptjavascript
Domain
full stackbackendfrontend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitRocket.Chat development setup
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60