mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 06:55:52 +03:00
[GH-ISSUE #2389] Dynamic filter - or even static filter to further separate agents #1469
Labels
No labels
In Process
bug
bug
dev-triage
documentation
duplicate
enhancement
fixed
good first issue
help wanted
integration
invalid
pull-request
question
requires agent update
security
ui tweak
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tacticalrmm#1469
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 @Aghakoocholo on GitHub (Jan 19, 2026).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2389
Hello,
I really enjoy using the RMM—it works exceptionally well. I wanted to ask if you accept suggestions or ideas for potential improvements.
Specifically, I was wondering if it would be possible to add something like a Dynamic Filter or Dynamic Group feature to the RMM.
Use Case Scenario:
Currently, Tactical separates servers from workstations, but there’s no way to further filter, for example:
Having this capability would be extremely helpful for automating tasks such as patching or rebooting. For example, I could:
At the moment, all servers are patched together, and simultaneous reboots can cause issues.
If we could either manually create filters for automated tasks or dynamically generate them (e.g., if a server is a VM or has “Host” in its name), it would resolve about 90% of the challenges we currently face with Tactical.
Please let me know your thoughts and whether this could be feasible.
Thank you,