mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
It should not be possible to select an end-of-maintenance date in the past compared to the start-up date #3450
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#3450
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 @FlorentPoinsaut on GitHub (Jul 5, 2024).
📑 I have found these related issues/pull requests
A maintenance end date can be chosen in the past compared to the start-up date.
🛡️ Security Policy
Description
👟 Reproduction steps
Create a maintenance and choose an end date in the past compared to the start-up date.
👀 Expected behavior
An error must appear and the user cannot validate the form.
😓 Actual Behavior
The user can create a maintenance with an end date in the past compared to the start-up date.
🐻 Uptime-Kuma Version
1.23.13
💻 Operating System and Arch
Debian 12
🌐 Browser
Firefox 115.12.0esr (64 bits)
🖥️ Deployment Environment
📝 Relevant log output
No response