BulkActions #2003

Closed
opened 2026-02-28 02:39:52 -05:00 by deekerman · 4 comments
Owner

Originally created by @ConradoP on GitHub (Mar 15, 2023).

⚠️ Please verify that this feature request has NOT been suggested before.

  • I checked and didn't find similar feature request

🏷️ 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

Originally created by @ConradoP on GitHub (Mar 15, 2023). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ 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_
Author
Owner

@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".

@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".
Author
Owner

@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?) ^^

@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?) ^^
Author
Owner

@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.

@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.
Author
Owner

@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.

@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 - #455 or - #1323 as there is no functional difference ⇒ I am going to close this as a duplicate.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#2003
No description provided.