Tickets - Policy settings
The per-org knobs on the Tickets feature. Most of the timing knobs that affect ticket creation live on the health monitor side; only enablement and retention live here. For organizational admins.
Where the settings live
Settings → Tickets. Admin-only.
The fields
Enable tickets
The master switch. Off means:
- No new tickets land — health-monitor and workflow attempts to open a ticket no-op.
- No auto-resolves run.
- Existing rows in the Tickets list remain readable, but they don't change state.
Within ~60 seconds of toggling, the change takes effect. Useful for incident response (silence everything quickly) or during a multi-day maintenance window.
Resolved-ticket retention (days)
How long Resolved tickets are kept before they're auto-deleted by the retention sweep. Range 5–365, default 365. Open and In Progress tickets are never retention-deleted regardless of age. See Retention.
What's on the health monitor side
If you came here looking for debounce windows, the flap threshold, or the reopen window — those govern ticket creation and live on the health monitor:
The split is deliberate: the timing knobs are about when the monitor decides a subject is firing; the tickets feature owns its own enable/retention semantic.
Note: The health monitor's per-org Publish tickets switch is independent of the Enable tickets switch here. Both have to be on for health-monitor events to produce tickets.