P4DTI issue job000047

TitleHistorical bugs are replicated but uninteresting
Assigned userNick Barnes
DescriptionAt startup, the replicator replicates all issues from the DT starting at the beginning of time. This takes a long time, uses up space, clutters up databases, and is usually unnecessary. RB 2000-11-21
This now only affects the Bugzilla integration. RB 2000-12-04
AnalysisWe should also only replicate issues which are created or modified after a configured date, which is the time of first installation by default, and we should document how to set this time earlier. Most people don't need all their historical issues replicated. RB 2000-11-21
bugzilla.py:latest_complete_replication() should return self.now() instead of '0'. NB 2000-11-29
How foundmanual_test
Evidence<http://www.ravenbrook.com/project/p4dti/doc/2000-11-01/quokka-alpha-test/> item 9
Observed in0.3.2
Test procedure<http://www.ravenbrook.com/project/p4dti/master/test/test_p4dti.py>, section 8.1
Created byRichard Brooksby
Created on2000-11-21 16:10:54
Last modified byGareth Rees
Last modified on2001-12-10 19:01:16
History2000-11-21 RB Created from sources (see evidence)
2000-12-04 RB Incorporated analysis from duplicate job job000096.


Change Effect Date User Description
5933 closed 2000-12-13 13:05:36 Nick Barnes        Don't replicate historical bugs (job000047)
5484 open 2000-12-05 20:08:21 Gareth Rees The TeamTrack integration now starts replicating TeamTrack data from the moment it is installed and not from the beginning of time.