# Archive flag for tickets

**URL:** https://community.zammad.org/t/archive-flag-for-tickets/20923
**Category:** Feature requests
**Created:** [August 28, 2026, 8:19am UTC](https://community.zammad.org/t/archive-flag-for-tickets/20923 "2026-08-28T08:19:50Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![rolfschmidt](https://community.zammad.org/user_avatar/community.zammad.org/rolfschmidt/32/3368_2.png) [@rolfschmidt](https://community.zammad.org/u/rolfschmidt)
#### Post date: [August 28, 2026, 8:19am UTC](https://community.zammad.org/t/archive-flag-for-tickets/20923/1 "2026-08-28T08:19:51Z")

</div>

### Archive flag for tickets

**1) What is your original issue/pain point you want to solve?**

Tickets can only be kept or deleted; there is no in-between. Deletion destroys the data.

**2) Which are one or two concrete situations where this problem hurts the most?**

Tickets subject to audit and retention requirements — old tickets must disappear from daily work (overviews, search defaults) but remain retrievable and intact.

**3) Why is it not solvable with the Zammad standard?**

Workarounds like an “archived” state require excluding it in every overview, search and report, which is fragile; deletion violates retention requirements.

**4) What is your expectation/what do you want to achieve?**

An archive flag that removes a ticket from normal operation (hidden from overviews/search defaults, effectively disabled) without actually deleting it.

Ticket#10231017