Mass edit monitors #593

Closed
opened 2026-02-28 01:51:39 -05:00 by deekerman · 6 comments
Owner

Originally created by @streamthing on GitHub (Nov 26, 2021).

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

  • I checked and didn't find similar feature request

🏷️ 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 selected button.

Alternatives

No response

📝 Additional Context

No response

Originally created by @streamthing on GitHub (Nov 26, 2021). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ 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 selected` button. ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_
deekerman 2026-02-28 01:51:39 -05:00
Author
Owner

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

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

@edrock200 commented on GitHub (Oct 18, 2022):

Another +1 for this feature.

@edrock200 commented on GitHub (Oct 18, 2022): Another +1 for this feature.
Author
Owner

@x86dev commented on GitHub (Jul 10, 2023):

+1 as well, would love this feature.

@x86dev commented on GitHub (Jul 10, 2023): +1 as well, would love this feature.
Author
Owner

@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.23 release
PRs implementing this feature should be based on said PR.

@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](https://github.com/louislam/uptime-kuma/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc). 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.23` release](https://github.com/louislam/uptime-kuma/milestone/34) PRs implementing this feature should be based on said PR.
Author
Owner

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

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

@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.
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#593
No description provided.