[GH-ISSUE #2382] Manual override for check #3409

Open
opened 2026-03-14 07:17:30 +03:00 by kerem · 0 comments
Owner

Originally created by @RoxasSora1233457879898484108743087 on GitHub (Dec 23, 2025).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2382

Our workflow is as follows.
When a check from the client or server turns red, we create a ticket in which the problem is addressed and resolved.

Currently, a check that fails remains red throughout the entire process of solving the problem. This makes the tactical status almost always red.

Therefore, it would be very practical to manually override a check that is currently red, so that it turns green again.

Furthermore, it would be good if we could temporarily limit this override, for example to one day or one week.

Originally created by @RoxasSora1233457879898484108743087 on GitHub (Dec 23, 2025). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2382 Our workflow is as follows. When a check from the client or server turns red, we create a ticket in which the problem is addressed and resolved. Currently, a check that fails remains red throughout the entire process of solving the problem. This makes the tactical status almost always red. Therefore, it would be very practical to manually override a check that is currently red, so that it turns green again. Furthermore, it would be good if we could temporarily limit this override, for example to one day or one week.
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#3409
No description provided.