-
-
Notifications
You must be signed in to change notification settings - Fork 463
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
One-off custom notification support #3559
Comments
Would also be nice to have an option with the notifications for mass email to the emails associated with the users plex account if signed in via plex. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
bump because I believe this is a useful feature. |
I agree, would love this feature too |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Can we keep this open? |
Bump, would love to see this come to fruition! |
Bump, this will be such a useful feature |
Why is this not a thing yet? |
Bump, really need this |
Bump. Overseerr is my pane of glass for my users. It would be very useful to communicate updates or send maintenance notifications as Overseerr already aggregates their email addresses. |
As this looks like it won't be implemented, I'm unsubscribing. |
Description
When it comes to notifications, we are currently limited to the pre-existing default notifications, we cannot send any custom notifications to our users.
Desired Behavior
Add the ability to send your own custom one-off notifications to specific users, same way that Ombi allows. There's a similar issue #405 but it's more about customising the existing default notifications.
This request is about just selecting some users, typing some text, and sending it as a notification.
Additional Context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: