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>
2 lines
137 B
SQL
2 lines
137 B
SQL
ALTER TABLE `alert_tickets` ADD `ticket_closed_at` text;--> statement-breakpoint
|
|
ALTER TABLE `alert_tickets` ADD `ticket_closed_by` text; |