Bulk close can close the osTicket tickets; Alerts top-level, Records group
Closing several alerts together can now also close their osTicket tickets (one by one, each written on its incident and in the audit log; one that fails does not stop the rest; Undo does not reopen tickets). The single and bulk close share one helper. Alerts moves to the top of the sidebar, and Monthly report and Change log move to a new Records group. Docs updated. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
215c0de8bf
commit
78822346b1
13 files changed
+234
-37
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. **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'.
|
||||
under Settings → Notifications → Alert tickets, which is admin-only. **Closing a ticket** along with an alert (the tick box in the Close drawer, for one alert or several picked together) 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