Tickets - Retention
How long resolved tickets are kept, what gets auto-deleted, and how to tune the retention period for your org. For organizational admins.
What gets auto-deleted
A background retention sweep runs hourly and deletes:
- Every Resolved ticket whose resolution time is older than the configured retention window.
- The full timeline for those tickets (every event removed alongside the ticket).
What's never auto-deleted:
- Open tickets — never. An old open ticket is a signal, not noise.
- In Progress tickets — never. Someone said they're on it.
- Resolved tickets within the retention window.
- Your per-org running numbers — sequences never reset, so
#42stays uniquely yours.
The default
365 days. A team can look back a year for "did this device do this last winter?" without changing the setting.
Tuning
Settings → Tickets → Resolved-ticket retention (days). Range 5–365.
- Lower retention (30–90 days) suits teams that triage and forget; postmortems happen elsewhere.
- Higher retention (180–365 days) suits teams that mine the ticket history for recurring incidents and trends.
Changes take effect on the next hourly sweep.

Organization deletion
When an organization is removed from Neowit, every ticket in it is deleted along with it. This is irreversible — if you want a copy of the tickets, export them before the organization is removed.
What you don't need to do
- Manual purges. The hourly sweep is idempotent and runs on every replica; no admin maintenance.
- Backup before tuning. Changing retention doesn't immediately delete rows — the sweep picks them up on the next hour.