Add the Alert tickets settings page, and show each alert's ticket on the Alerts page
Settings -> Alert tickets: switch it on, choose the osTicket integration (only ones with a ticket API set up can be chosen), who the tickets come from, help topic and priority, which severities and kinds, how long a problem must last, when many become one summary ticket, how long a return counts as the same problem, and what to do about problems already there. Buttons to send a test ticket and to check now, and a line saying what the last check did. Server messages (a missing integration, a refused key) are shown as they are. The Alerts page shows "Ticket #123" on an alert that has one, linking to it in osTicket, and a Ticket column in the CSV export. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
467d1a1a06
commit
96c93ef924
6 files changed
+372
-2
No files matched your search
@@ -226,6 +226,10 @@ export default function Privacy() {
|
||||
{outbound && outbound.integrationTypes.length > 0 ? ` (${outbound.integrationTypes.join(", ")})` : ""} — API calls to systems
|
||||
you configured, to read status and, when someone with permission asks, to act (start a VM, run a template…).
|
||||
</li>
|
||||
<li className="mb-2">
|
||||
<strong>osTicket tickets</strong> — only if an admin has switched on Settings → Alert tickets: for a problem that has lasted, the text of the alert
|
||||
(which server or integration, what is wrong), a link back to this app, and the requester name and email set there go to your osTicket's API.
|
||||
</li>
|
||||
<li className="mb-2">
|
||||
<strong>DNS providers</strong>
|
||||
{outbound && outbound.dnsProviderTypes.length > 0 ? ` (${outbound.dnsProviderTypes.join(", ")})` : ""} — zones and records are read
|
||||
|
||||
Reference in new issue
Block a user