On 19.11.23 19:31, Florian Berger wrote:
Over time, a busy Trac instance (think agile) accumulates a lot of tickets, milestones, and
associated metadata such as components or versions.
[...]
So, I am thinking about strategies for archiving. That means I want to be able to easily access and
search old content [...], but remove it from the running
instance without interrupting current data [...].
The best plan I've come up with so far is to set up a second Trac instance, and then using some SQL
trickery to move the obsolete data to that instance, removing it from the current one. That way,
ticket numbers etc. should be preserved, while the original instance should continue to operate as
usual, i.e. incrementing ticket numbers correctly.
As this has not attracted attention, and I want to start the work next week, again my question: Does
anyone, or has anyone ever done, regular ticket/milestone/component/... cleanup? If so, using which
strategy?
My Trac instance has been running since 2017, has 906 tickets, 440 milestones, 18 components, and 11
versions. I am sure there must be way larger instances, where e.g. ticket and milestone searches
must become progressively confusing, and where stale compoments clutter ticket creation.
Any reports and experiences are welcome.
Thanks,
Florian
--
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/trac-users/7a07d9bb-9cb9-4d1d-8b16-3ebeea6dc353%40posteo.net.
