mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
E-Mail Subscription by Status-Page #2073
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#2073
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @pavl21 on GitHub (Apr 4, 2023).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
New Notification, Other
🔖 Feature description
Provide an option on the status page to send an e-mail when the status changes. As well as a message to all subscribers when there is maintenance work.
✔️ Solution
E-Mail Subscription via Status-Page and SMTP-Configuration
❓ Alternatives
No response
📝 Additional Context
No response
@CommanderStorm commented on GitHub (Jun 12, 2023):
@pavl21 is this a duplicate of https://github.com/louislam/uptime-kuma/issues/916?
If no, could you make this issue more distinct?
If yes, could you close this issue? (duplciates only hurt the project)
@CommanderStorm commented on GitHub (Dec 3, 2023):
@pavl21
We are consolidating duplicate issues a bit to make issue management easier.
I think, we should track this issue in #916 as there is no functional difference and the other isuse has more support and a deeper discussion
⇒ I am going to close this as a duplicate