Over time, a busy Trac instance (think agile) accumulates a lot of tickets, milestones, and
associated metadata such as components or versions.
Especially when the need arises to search passed milestones or completed tickets, this may lead to
very long result lists including very old data. I may want to search 1 year back, but not 8 years.
Also, the "new ticket" form somewhat degrades in usability when there are components which are no
longer being used, or versions that are long released.
Simply deleting old tickets, milestones etc. is not an option if one wants to preserve project history.
So, I am thinking about strategies for archiving. That means I want to be able to easily access and
search old content (so a pure headless db backup would not suffice), but remove it from the running
instance without interrupting current data (so backing up at some point and setting up a fresh
environment is not an option).
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.
I haven't actually tried it, but looking at the db it seems certainly possible.
I've done a brief web search on the topic, but have not found Trac-specific resources.
Does anyone else do archiving of Trac tickets etc.?
If so, using which procedure?
Does mine sound doable? Anything I am overlooking?
Is there any documentation I am not aware of?
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 trac-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/98caf4d2-5d3f-4b47-b316-9d902039b868%40posteo.net.
associated metadata such as components or versions.
Especially when the need arises to search passed milestones or completed tickets, this may lead to
very long result lists including very old data. I may want to search 1 year back, but not 8 years.
Also, the "new ticket" form somewhat degrades in usability when there are components which are no
longer being used, or versions that are long released.
Simply deleting old tickets, milestones etc. is not an option if one wants to preserve project history.
So, I am thinking about strategies for archiving. That means I want to be able to easily access and
search old content (so a pure headless db backup would not suffice), but remove it from the running
instance without interrupting current data (so backing up at some point and setting up a fresh
environment is not an option).
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.
I haven't actually tried it, but looking at the db it seems certainly possible.
I've done a brief web search on the topic, but have not found Trac-specific resources.
Does anyone else do archiving of Trac tickets etc.?
If so, using which procedure?
Does mine sound doable? Anything I am overlooking?
Is there any documentation I am not aware of?
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 trac-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/98caf4d2-5d3f-4b47-b316-9d902039b868%40posteo.net.