[GH-ISSUE #2387] [Feature Request] - Implement Name/Regex based Patch Policy #1468

Open
opened 2026-03-02 02:23:19 +03:00 by kerem · 0 comments
Owner

Originally created by @ghosty22 on GitHub (Jan 18, 2026).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2387

Hi,

i am using tacticalRMM for about 2 years now and i always approve patches manually except the criticals. But i am missing a option in patching policies that enables me to approve patches based on thier title or body text with either a "contains" filter or a RegEx filter. Updates that are like the security definitions are very frequent and could be approved automatically but are in the category "other" so just a policy for that would hit way to many and maybe risky patches.

Also i could try to implement such a feature myself but i have no idea about the project structure and if this fits the strategy of the project. So either if that could be implemented would be nice or to give me a start where i can implement this.

Thank you in advance :)

Originally created by @ghosty22 on GitHub (Jan 18, 2026). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2387 Hi, i am using tacticalRMM for about 2 years now and i always approve patches manually except the criticals. But i am missing a option in patching policies that enables me to approve patches based on thier title or body text with either a "contains" filter or a RegEx filter. Updates that are like the security definitions are very frequent and could be approved automatically but are in the category "other" so just a policy for that would hit way to many and maybe risky patches. Also i could try to implement such a feature myself but i have no idea about the project structure and if this fits the strategy of the project. So either if that could be implemented would be nice or to give me a start where i can implement this. Thank you in advance :)
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/tacticalrmm#1468
No description provided.