mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Monitor Group bulk add #2490
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#2490
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 @VashStampedeTRI14 on GitHub (Aug 18, 2023).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
UI Feature
🔖 Feature description
Looking for a feature in the settings similar to "Tags" but for monitor groups. This way you can bulk add multiple into a group instead of one at a time upon creation.
✔️ Solution
Be able to go in to settings and select Monitor Group. From here you can create a new monitor group and/or bulk add monitors to that group or an existing group.
❓ Alternatives
No response
📝 Additional Context
No response
@CommanderStorm commented on GitHub (Aug 18, 2023):
I think this is a duplicate of https://github.com/louislam/uptime-kuma/issues/1457 or https://github.com/louislam/uptime-kuma/issues/1323
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?) ^^
@VashStampedeTRI14 commented on GitHub (Aug 18, 2023):
Ah sorry did not see these when searching "Monitor Group". I agree this is duplicate of #1457. Closing this out. Thank you!