mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Notification time zone I would like to refer to the general settings. #1013
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#1013
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 @Vampire-V on GitHub (Apr 22, 2022).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
New Notification
🔖 Feature description
Notification time zone I would like to refer to the general settings.
✔️ Solution
Notification time zone I would like to refer to the general settings.
❓ Alternatives
No response
📝 Additional Context
No response
@Computroniks commented on GitHub (Apr 22, 2022):
This seems more of a bug than a feature. Or at least an issue with the way that the notification system handles time. However, this might be quite lengthy to fix as it seems most notification providers directly use
Date.now()for their time instead of using the setting.@liuchisanren commented on GitHub (May 6, 2022):
I also found this problem. Whether it is setting the container time zone or the time zone in the Uptime Kuma settings, the time zone in the alarm is still the default. I hope the developer can solve this problem as soon as possible.
@louislam commented on GitHub (May 9, 2022):
Duplicate of #40