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
@@ -112,7 +112,7 @@ even further, to admin only:
|
||||
- **Alert tickets**: everyone sees which alerts have an osTicket ticket (a
|
||||
badge on the Alerts page, linking to the ticket in osTicket); switching the
|
||||
feature on, choosing what opens a ticket, and sending a test ticket are
|
||||
under Settings → Notifications → Alert tickets, which is admin-only.
|
||||
under Settings → Notifications → Alert tickets, which is admin-only. **Closing a ticket** along with an alert (the tick box in the Close drawer) is an operator's, like closing the alert; the login it writes with, and **Test closing**, are administrators'.
|
||||
- **Runbooks**: everyone reads them (on a server's page, an integration's card,
|
||||
next to an alert); writing, editing and removing one needs operator.
|
||||
- **Inventory**: everyone can see the hardware (and print its labels); adding, editing and removing needs
|
||||
|
||||
Reference in new issue
Block a user