mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 23:15:57 +03:00
[GH-ISSUE #988] Windows Update - Add more time options to scheduled patching e.g. "first, second, Last <weekday> of Month" #599
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#599
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 @bcredeur97 on GitHub (Feb 24, 2022).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/988
Originally assigned to: @sadnub on GitHub.
The default time options for doing scheduled patches is only "Daily/weekly" OR monthly, but on a specific numbered day of the month. This is a bit frustrating because sometimes I want to update machines on the last Saturday of every month, gives a window for issues with Windows updates to be sorted out before machines are patched.
If an option could be added to add a picker that lets you do first/second/third/fourth/last with a specific weekday choice. That way no matter how the days fall you know exactly when you're machines are going to get patched in a given month.
@silversword411 commented on GitHub (Mar 16, 2022):
Workaround for now: Every 1st of the month just change the date to whatever is the day you want till we have enhanced scheduler in updates area
@Meganitrospeed commented on GitHub (Apr 11, 2022):
As an idea, why not support cron schedule expressions? That would allow it a lot more flexibility
@silversword411 commented on GitHub (Apr 12, 2022):
That's a linux-only feature, and probably should be in its own issue for tracking...because I'm sure it'll be added at some point :)
@silversword411 commented on GitHub (Jun 24, 2022):
Ticket Consolidation: Combining into https://github.com/amidaware/tacticalrmm/issues/1188