Opened 7 years ago

Closed 5 years ago

#7864 closed task (fixed)

Purge old RT tickets

Reported by: runa Owned by: lunar
Priority: Medium Milestone:
Component: User Experience/Tor Support Version:
Severity: Keywords:
Cc: mo, runa Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Moritz suggested that we purge old RT tickets from time to time to avoid sitting on lots of personal data, email addresses, and so on. I would imagine that this is easy to do with a cron on the same server and poking at the DB a bit. Thoughts?

Child Tickets

Change History (13)

comment:1 Changed 7 years ago by mo

RT seems to come with a command line utility/lib called RTx-Shredder to purge tickets from the database. The example does not show how to apply a time limitation ("old" tickets), and from the documentation it is not clear whether there is an option to do so. One would have to run it to see which plugins it lists and what they offer.

comment:2 Changed 7 years ago by weasel

Seems like a horrible idea to rewrite/destroy part of the debugging/change log history.

comment:3 Changed 7 years ago by weasel

Resolution: wontfix
Status: newclosed

comment:4 Changed 7 years ago by arma

Resolution: wontfix
Status: closedreopened

reopening since weasel said he didn't realize this was about rt

comment:5 Changed 7 years ago by phobos

We'll need to provide stats on help desk utilization for various contracts. Before we purge, we should figure out what the stats are, and get them.

comment:6 Changed 7 years ago by runa

What kind of stats do you want?

comment:7 Changed 6 years ago by weasel

Please provide guidance on what to delete.

Would something like
rt-shredder --plugin "Tickets=query,(Status = 'resolve' OR Status = 'rejected') AND LastUpdated < '90 days ago'"
be what you want?

comment:8 Changed 6 years ago by weasel

Status: reopenedneeds_information

comment:9 Changed 6 years ago by phobos

We shouldn't purge tickets until we have finalized the work and summary data for the projects. This also purges past history of work performed and provides a trail of who does what.

comment:10 Changed 6 years ago by phobos

Further, we lose the history of communications and discussions about tickets.

comment:11 Changed 5 years ago by lunar

Component: Tor Sysadmin TeamTor Support
Owner: set to lunar
Status: needs_informationassigned

I was not aware of this ticket and restarted the discussion on the tor-internal mailing list. Hopefully we will agree on the right way to do it.

Last edited 5 years ago by lunar (previous) (diff)

comment:12 Changed 5 years ago by lunar

Status: assignedneeds_information

comment:13 Changed 5 years ago by lunar

Resolution: fixed
Status: needs_informationclosed

This is now implemented. Tickets will be removed from the database after 100 days of inactivity.

Note: See TracTickets for help on using tickets.