-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Archiving and Data Retention Policy #524
Comments
I've always felt that having a ticket system is not just about work flow but about tracking instances of problems and problem history. Deleting closed tickets would break that and ruin reporting. What is your logic/rational for such a feature besides database size? |
My only counter to that would be that I have no issue having the default be that the pruning of Closed tickets be off.. But it would still be a nice feature to have especially as we are using it w/ significant attachments.. and those attachments eat space. Especially w/ 50 ~tickets a day and 2-5mb / ticket... as it is right now.. i am logging in monthly and purging legacy closed tickets.. I just want to automate the process.. |
I would love to see an option for "Purge tickets closed more than X days/months/years ago". This way tickets that no longer need to be kept for logging or policy reasons can be dropped to keep the system cleaned up and relevant. |
@mrabino1 You could just dump the attachments. (and starting in 1.8.1 you could use the filesystem plugin for attachments. So then you would just have to delete the contents of the directory) @slm4996 I wouldn't mind a feature similar to that, especially if there was a way to manually trigger the clean up also. (ie I would disable it and probably run a cron/batch to check once a yearly for anything over 2 years.) |
Everyone - We don't have the details ironed out yet, but we're planning on adding an archiving feature. |
Any update or guidance on when this feature might on the roadmap? thx. /mr |
Not at this time. |
Peter is proposing #1094 which will make its way somewhere into the 1.9.x series (we think). This adds the ability to define new statuses and adds two base statuses, "archived" and "deleted". Because we currently only have "open" and "closed" major states, we're very limited on what we can implement with respect to retention. Once #1094 gets merged, we will work on or consider a plugin to implement the archiving and purging of old tickets according to configurable criteria. For @ntozier, not installing the plugin would allow for infinite retention of tickets. |
On a similar note to purging logs, will you consider having a Purge Closed tickets feature? This will assist in keeping the database from getting out of control in size. thx..
The text was updated successfully, but these errors were encountered: