RocketChat/Rocket.Chat

Settings for confirmation for using @all notification on messages

Open

#909 opened on Sep 26, 2015

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

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

Tech stack
typescriptreactnodejs
Domain
frontendbackend
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.
mostly clear
Prerequisites
Familiarity with Rocket.Chat settingsBasic understanding of @all notifications
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate how existing settings are implemented in Rocket.Chat (e.g., in the Settings module). Look at the codebase for @all notification handling, likely in message or notification services. Propose a UI for a confirmation dialog and a setting toggle. Consider the number of users/timezone rules as mentioned in the issue.