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
@@ -170,6 +170,9 @@ export const INTEGRATION_FIELDS: Partial<Record<IntegrationType, IntegrationFiel
|
||||
},
|
||||
{ key: "apiKey", label: "Ticket API key (optional)", secret: true, optional: true, type: "password" },
|
||||
{ key: "apiInsecure", label: "Allow self-signed certificate (ticket API)", secret: false, type: "checkbox" },
|
||||
// Only for closing a ticket from the Alerts page. osTicket's API cannot close tickets, so this writes to its database (src/integrations/osticket/closeTicket.ts): a separate login, never the read-only one above.
|
||||
{ key: "closeUsername", label: "Database username for closing tickets (optional)", secret: false, optional: true, placeholder: "a separate user that may update tickets — see INTEGRATIONS.md" },
|
||||
{ key: "closePassword", label: "Database password for closing tickets (optional)", secret: true, optional: true, type: "password" },
|
||||
],
|
||||
};
|
||||
|
||||
|
||||
Reference in new issue
Block a user