mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
BulkActions #2003
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#2003
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 @ConradoP on GitHub (Mar 15, 2023).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
Other
🔖 Feature description
Bulk Actions
✔️ Solution
Good morning, please could you include BulkActions for url import/export and contact alert changes?
❓ Alternatives
No response
📝 Additional Context
No response
@magnusviri commented on GitHub (May 10, 2023):
I would love this feature as well. I was using the backup feature by modifying the backup and then restoring the modification, but with a lot of monitors, I haven't been able to get it to "restore".
@CommanderStorm commented on GitHub (Jul 27, 2023):
I think this is a duplicate of https://github.com/louislam/uptime-kuma/issues/455 (or depending on what you mean https://github.com/louislam/uptime-kuma/issues/1457 which is clearer in what needs to be implemented)
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?) ^^
@jaxjexjox commented on GitHub (Aug 1, 2023):
Agree, this is duplicate of other bulk action requests, which at this point now seems to be a very in demand change.
@Conradop please consider closing this and "bumping"the other original bulk edit requests.
@CommanderStorm commented on GitHub (Dec 4, 2023):
@ConradoP
We are consolidating duplicate issues a bit to make issue management easier.
I think, we should track this issue in
as there is no functional difference
⇒ I am going to close this as a duplicate.