Osticket archive downloads

We have over tickets [in our largest production site] and I haven't found any reason to archive or delete tickets yet. That's right, it is mine, and this isn't the support Forum for third party plugins. Although I'm sure by "no support" you mean: "no support for v1.

I'll get around to updating the plugin soon, I do it in my spare time, which is getting rarer. This site is best viewed in a modern browser with JavaScript enabled.

The closed tickets and their attachments archived to the disk are irrevocably deleted from the database. Since the archived copy is a simple JSON dump file with just the necessary information, it is not possible to restore the archived data back to the database.

Only use this utility if you are trying to reduce your database size by permanently archiving old tickets. Take a look at sample. Attachments are stored in the attachments directory with filenames in the following format.

The author provides no guarantees or warranties and is not liable for the outcome stemming from the use of the program.

Skip to content. Star 5. Branches Tags. Could not load branches. Could not load tags. Plugin for osTicket which can automatically archive tickets before delete, and allows for auto-pruning of old tickets.

Enables PDF Archiving of tickets before they delete, and a basic auto-delete of old tickets via schedule. Configure it as you need for your environment. How old is too old? If you specify an max-age for closed tickets, the plugin will delete them for you when the maximum age you specify is reached.

We store when it last ran the purge, and depending on your settings, will run it again provided cron is called often enough. EG: If you want it to run every 12 hours, but only run cron every 24, not much we can do about that. How many tickets do we purge every time we run? Depending on how you've configured it, this can be high command-line mode for this or low for auto-cron , if you have a high-volume of tickets and auto-cron, you will need to set this to run as often as possible. If you change to a version not provided, or update etc, then use the above method instead and open an issue so I can make a new version.

After each update, go into the plugin settings and push Save, this will check that the Signal is still there, otherwise it will need to be added again.