mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Mass edit monitors #593
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#593
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 @streamthing on GitHub (Nov 26, 2021).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
UI Feature
🔖 Feature description
Select few monitors and change it in one click...
For now i need to click one monitor, edit, change value, save.
Click next, next next.
Just mass settings edit.
heartbeat, check times, notifications rules etc.
✔️ Solution
UI with checkbox on monitor and
Edit selectedbutton.❓ Alternatives
No response
📝 Additional Context
No response
@asdfok commented on GitHub (Dec 1, 2021):
+1 with this. Few days ago, I had to sort out some of the lists and re-group it. Took me few hours to finish, because of the "Drag and Drop" from hundred of lists and multiple Groups is not easy.
@edrock200 commented on GitHub (Oct 18, 2022):
Another +1 for this feature.
@x86dev commented on GitHub (Jul 10, 2023):
+1 as well, would love this feature.
@CommanderStorm commented on GitHub (Jul 10, 2023):
@x86dev @edrock200
Please refrain from posting
+1/ requests for updates things on issues, as this makes issue-management harder.Issues are for discussing what needs to be done how by whom.
We use 👍🏻 on issues to prioritise work.
Related PR that implements part of this issue: https://github.com/louislam/uptime-kuma/pull/1886
The mentioned PR is slated to be merged into the
1.23releasePRs implementing this feature should be based on said PR.
@CommanderStorm commented on GitHub (Jul 27, 2023):
@streamthing
I think this is a duplicate of https://github.com/louislam/uptime-kuma/issues/455
If you agree, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage?
If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?) ^^
@CommanderStorm commented on GitHub (Dec 5, 2023):
@streamthing
We are consolidating duplicate issues a bit to make issue management easier.
I think, we should track this issue in #455 as there Mass editing and bulk editing are essentially the same thing
⇒ I am going to close this as a duplicate.