Close the osTicket ticket along with an alert
The Close drawer can also close the alert's osTicket ticket. osTicket's API cannot, so this writes to its database with a separate, optional login: the ticket is set to Closed, a note in its thread says who closed it and why, and the closed event is recorded, in one transaction. Tables and columns are checked first, only an open ticket is closed, and a ticket closed by somebody else at the same moment is left alone. Summary tickets are not closed from here. "Test closing" (Alert tickets settings) tries every write and rolls it back. If the ticket cannot be closed the alert is still closed and the reason is said, noted on the incident and audited. Not run against a real osTicket: tested against a pretend database only. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
a94899865e
commit
5ae61a1ece
21 files changed
+8405
-23
No files matched your search
@@ -781,6 +781,8 @@ export const alertTickets = sqliteTable(
|
||||
lastSeenAt: text("last_seen_at").notNull(), // ISO
|
||||
ticketedAt: text("ticketed_at"), // ISO; when the ticket was opened
|
||||
clearedAt: text("cleared_at"), // ISO; null while the alert is still active
|
||||
ticketClosedAt: text("ticket_closed_at"), // ISO; when this app closed the ticket in osTicket (or found it already closed when asked to)
|
||||
ticketClosedBy: text("ticket_closed_by"), // who asked, as a name
|
||||
},
|
||||
(t) => [index("alert_tickets_key_idx").on(t.alertKey)],
|
||||
);
|
||||
|
||||
Reference in new issue
Block a user