starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

Quality of life: pre-fill some information for "Schedule maintenance" form #3892

New issue

Closed

opened 2026-02-28 03:44:17 -05:00 by deekerman · 5 comments

deekerman commented

2026-02-28 03:44:17 -05:00

Owner

Originally created by @MaddyGuthridge on GitHub (Jan 13, 2025).

Couldn't find anything, searched open issues for terms such as "maintenance", "form" and "edit"

🏷️ Feature Request Type

Maintenance

🔖 Feature description

When I want to schedule maintenance, it is quite tedious to have to fill out all the details every time. Some simple "best guess" pre-filling of the information would go a long way towards making it quick and easy to schedule maintenance.

✔️ Solution

Pre-fill the following values:

Timezone: the time zone of the client filling the form, since that's probably the time zone their brain will be thinking in
Start date/time: the current date/time
End date/time: the current date/time

While these values are not perfect, they are a good starting point, which would make the process much faster for scheduling maintenance, especially in cases where few modifications are needed. For example, if I wanted to spend 10 minutes updating one of the apps running on my server, all I'd need to do would be enter a title, pick the affected monitors, then set an end date/time 10 minutes into the future, rather than filling out all information myself.

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @MaddyGuthridge on GitHub (Jan 13, 2025). ### 📑 I have found these related issues/pull requests Couldn't find anything, searched open issues for terms such as "maintenance", "form" and "edit" ### 🏷️ Feature Request Type Maintenance ### 🔖 Feature description When I want to schedule maintenance, it is quite tedious to have to fill out all the details every time. Some simple "best guess" pre-filling of the information would go a long way towards making it quick and easy to schedule maintenance. ### ✔️ Solution Pre-fill the following values: * Timezone: the time zone of the client filling the form, since that's probably the time zone their brain will be thinking in * Start date/time: the current date/time * End date/time: the current date/time While these values are not perfect, they are a good starting point, which would make the process much faster for scheduling maintenance, especially in cases where few modifications are needed. For example, if I wanted to spend 10 minutes updating one of the apps running on my server, all I'd need to do would be enter a title, pick the affected monitors, then set an end date/time 10 minutes into the future, rather than filling out all information myself. ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman

2026-02-28 03:44:17 -05:00

closed this issue
added the
feature-request

A:ui/ux

help wanted

good first issue
labels

deekerman commented

2026-02-28 03:44:23 -05:00

Author

Owner

@SniperAsh6 commented on GitHub (Jan 13, 2025):

A bonus taking this slightly further would be to have the option of common durations selectable (and configurable?) such as 15 mins, 1 hour and so on which could save even more interaction. And/or maybe even a 'Quick maintenance' type option from a monitor if it's only for a single one with those durations selectable

With the timezone field you mention, the default value is Same as Server Timezone which doesn't feel like a bad default

@SniperAsh6 commented on GitHub (Jan 13, 2025): A bonus taking this slightly further would be to have the option of common durations selectable (and configurable?) such as 15 mins, 1 hour and so on which could save even more interaction. And/or maybe even a 'Quick maintenance' type option from a monitor if it's only for a single one with those durations selectable With the timezone field you mention, the default value is `Same as Server Timezone` which doesn't feel like a bad default

deekerman commented

2026-02-28 03:44:23 -05:00

Author

Owner

@MaddyGuthridge commented on GitHub (Jan 13, 2025):

Huh I always need to manually select "same as server timezone"

@MaddyGuthridge commented on GitHub (Jan 13, 2025): Huh I always need to manually select "same as server timezone"

deekerman commented

2026-02-28 03:44:23 -05:00

Author

Owner

@Nightfirecat commented on GitHub (Sep 19, 2025):

Using v2.0.0-beta.4, I also see that the default selection is blank rather than Same as Server Timezone. (which would be much preferred) For me, creating a maintenance window with this blank selection ends up selecting UTC+0.

@Nightfirecat commented on GitHub (Sep 19, 2025): Using v2.0.0-beta.4, I also see that the default selection is blank rather than `Same as Server Timezone`. (which would be much preferred) For me, creating a maintenance window with this blank selection ends up selecting UTC+0.

deekerman commented

2026-02-28 03:44:23 -05:00

Author

Owner

@NerdyShawn commented on GitHub (Oct 20, 2025):

I agree the maintenance scheduling could be streamlined on what all ya need to input. Just the time input alone having to do input digit had me searching for an open issue, this would pair nicely with like a small calendar that pops up as a near date suggestion can click instead of only txt input. Give me a button to say "now" then I can tweak the values more easily. Perhaps some presets on the distance for the end time 1h, 4h, or 24h.

@NerdyShawn commented on GitHub (Oct 20, 2025): I agree the maintenance scheduling could be streamlined on what all ya need to input. Just the time input alone having to do input digit had me searching for an open issue, this would pair nicely with like a small calendar that pops up as a near date suggestion can click instead of only txt input. Give me a button to say "**now**" then I can tweak the values more easily. Perhaps some presets on the distance for the end time 1h, 4h, or 24h. <img width="831" height="158" alt="Image" src="https://github.com/user-attachments/assets/a53dfccd-ac7e-4e1e-901b-dffb841e7256" />

deekerman commented

2026-02-28 03:44:23 -05:00

Author

Owner

@kurama commented on GitHub (Jan 13, 2026):

Hi, I just finished working on the above, feel free to give me feedback 👍

@kurama commented on GitHub (Jan 13, 2026): Hi, I just finished working on the above, feel free to give me feedback :+1: