You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From #4984 (monitor → action → alert model): the reporter lists the alert targets they expect as Email / Teams / Webhook / Ticket, and in #4330 describes a reboot job that "creates a ticket … closes the ticket if online". Breeze has native ticketing, but an alert cannot become a ticket without a human:
alertRules / alertTemplates carry no ticket-creation field.
The only ticket↔alert link today is the reverse direction (an AI agent triggered by a ticket).
Proposed Fix
Two small, independently shippable pieces:
ticket notification channel type: config = board/queue, default priority mapping from alert severity, assignee/team, and a "one ticket per open alert" dedupe (key on alertId, like alertNotifications). Auto-resolve of the alert adds a closing comment and optionally closes the ticket.
Description
From #4984 (monitor → action → alert model): the reporter lists the alert targets they expect as Email / Teams / Webhook / Ticket, and in #4330 describes a reboot job that "creates a ticket … closes the ticket if online". Breeze has native ticketing, but an alert cannot become a ticket without a human:
NOTIFICATION_CHANNEL_TYPES=email, slack, teams, webhook, pagerduty, sms, pushover(packages/shared/src/constants/index.ts:43) — noticket.run_script, send_notification, create_alert, execute_command, deploy_software, ai_triage— nocreate_ticket.alertRules/alertTemplatescarry no ticket-creation field.The only ticket↔alert link today is the reverse direction (an AI agent triggered by a ticket).
Proposed Fix
Two small, independently shippable pieces:
ticketnotification channel type: config = board/queue, default priority mapping from alert severity, assignee/team, and a "one ticket per open alert" dedupe (key onalertId, likealertNotifications). Auto-resolve of the alert adds a closing comment and optionally closes the ticket.create_ticketautomation action: same payload, usable from any automation trigger (schedule/event), so workflows like "reboot batch started → open ticket → close when back online" become possible (Feature Reques Schedule Reboot and monitor I have a script that allows me more control over when server reboots are sche #4330, [Maintenance][Alerts] Post-window verification: alert (and ticket) when a device that was online before a maintenance window is still offline after it #5236).Both should respect the dual-axis ownership already on
notificationChannels/automations.Affected Files
packages/shared/src/constants/index.ts(NOTIFICATION_CHANNEL_TYPES),packages/shared/src/validators/index.ts(automation action union ~L238-273)apps/api/src/services/notificationDispatcher.ts(~L756-841 channel switch)apps/api/src/services/automationRuntime.ts(action executor)apps/api/src/db/schema/alerts.ts(channel enum), ticketing service for create/closeapps/web/src/components/alerts/channel editor,apps/web/src/components/automations/AutomationForm.tsxReported By
stressedout9064 on Discord (#feature-suggestions / #general, 2026-08-28 and 2026-08-30) — extracted from #4984 and #4330.