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
+1
-1
@@ -485,7 +485,7 @@ maintenance with it. A silenced problem is **not remembered as known**, so one s
|
||||
|
||||
Every time an alert was raised and later went away is an **incident**: when it opened and closed, how bad it got, what it was about, what explained it, who acknowledged or was handed it, and — on its
|
||||
timeline — what was done to the thing in the hour around it (maintenance, a restart, a settings change). People can add notes. The recorder looks at the alerts **every five minutes** whether or not anyone has
|
||||
the page open; the same alert coming back is a **new** incident. Resolved incidents are kept **400 days**. They are on **Operations → Alerts → History**, in the read API (`/api/v1/incidents`) and in the
|
||||
the page open; the same alert coming back is a **new** incident. Resolved incidents are kept **400 days**. They are on **Alerts → History**, in the read API (`/api/v1/incidents`) and in the
|
||||
monthly report.
|
||||
|
||||
### What changed before an incident
|
||||
|
||||
Reference in new issue
Block a user