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

Ensure all team members of an on-call policy have acceptable notification config #1809

Open
WillDaSilva opened this issue Jan 21, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@WillDaSilva
Copy link
Contributor

Is your feature request related to a problem? Please describe.
By default new OneUptime users don't have call/SMS notifications enabled. If one such user becomes the primary on-call, and OneUptime attempts to notify them, they may not receive the notification quickly enough.

Describe the solution you'd like
Visibility into the notification settings users in an on-call policy would allow us to ensure that everyone can and will receive call/SMS notifications if there is a high/critical severity incident, or a high severity alert.

As a bonus, it'd be nice if a OneUptime monitor could alert us if someone in the on-call policy does not have their notification settings set up in a way we desire, e.g. they're missing a verified phone number, or they don't have OneUptime configured to send them a phone call if a high severity incident/alert goes off.

Describe alternatives you've considered
A way for OneUptime project admins/owners to directly set the on-call notification settings for all member would be preferable, but more work to implement. In any case, you'd still need a way to ensure members have added & verified their phone number, so this issue would ideally be done before such a feature is implemented.

@WillDaSilva WillDaSilva added the enhancement New feature or request label Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant