mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 15:05:57 +03:00
[GH-ISSUE #997] Feature: Personal alerts #2549
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#2549
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 @bbrendon on GitHub (Mar 3, 2022).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/997
We don't use Tactical for alerting like someone normally would. We just use it to determine some basic health but nothing that requires any immediate action.
BUT
Techs would like to use the alerting to get notified when a computer goes offline/online to make it easier to contact users. It would also be very useful for people outside the timezone.
This is kinda related to
https://github.com/wh1te909/tacticalrmm/issues/427
But it feels like having one automation policy per tech would be overkill, though possibly a workable solution?
We don't use the checkboxes for the SMS/Email/Dashboard Alerts on the Dashboard table view. In my ideal world, those check boxes would email the person who checked the box. Kind of a “personal” alerting system.
@plao commented on GitHub (Mar 3, 2022):
+1 for me also!