Deleting/cleaning tickets


  • Used Zammad version: 3.6 (latest)
  • Used Zammad installation source: package
  • Operating system: CentOS 7
  • Browser + version:

Expected behavior:

After years of successful running, disk space is close to exhaustion. Analysis showed that it’s due to storage zammad folder, where attachments to files are stored.

To resolve the issue, it was decided to create a special queue and move junk tickets there and cleanup the queue periodically using Scheduler.

Actual behavior:

Scheduler action has been created, scheduler shows amount of tickets to be processed (deleted) on upcoming run, but tickets are not deleted after the run.

Steps to reproduce the behavior:

Create action delete for specified queue in Scheduler, schedule task and check the queue afterwards. All tickets will still be there.

Additional question - is there a better way to clean up tickets? We got a lot of spam for years and now I guess the time to clean it up. Any suggestions?

The best and safest way is to use UI options that are available.
This can either be the data privacy function which also removes the user in question or the scheduler.

The second part is in terms of “speed” and automated point of view the best way to approach this goal.
The scheduler removes up to 2000 tickets per run and runs in UTC time.

So if you have a ton of tickets, you’ll need to wait for it to finish.
As this post is a bit older by now this should show.

If not, you may want to inspect your production.log for errors, because at this point all we can do is to guess what’s wrong.

That’s right on the spot, thank you @MrGeneration. Indeed it works in small batches, so to see results we needed some time and patience

1 Like

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.