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
+1
-1
@@ -284,7 +284,7 @@ It runs the checks live when opened (a recent result is reused for a minute), an
|
||||
## Tickets in osTicket
|
||||
|
||||
Not a notification, but it acts on the same alerts: with **Settings → Notifications → Alert tickets** switched on (off by default), a problem on the Alerts page opens a
|
||||
ticket in osTicket. It runs every 15 minutes, starting about a minute and a half after the app starts.
|
||||
ticket in osTicket. It runs every 15 minutes, starting about a minute and a half after the app starts. It never closes a ticket by itself; closing is something you choose, in the Close drawer on the Alerts page, when the integration has a separate database login for it (see INTEGRATIONS.md).
|
||||
|
||||
| Rule | What it means |
|
||||
|---|---|
|
||||
|
||||
Reference in new issue
Block a user