P4DTI issue job000014

TitleEdited filespecs aren't replicated from TeamTrack to Perforce
Assigned userGareth Rees
DescriptionWhen a filespec is changed, the modification time (TS_TIME1) is not set in the record in the TS_VCACTIONS table. This means that the replicator won't be able to detect changed filespecs in TeamTrack, and the databases will be inconsistent.
AnalysisThis defect is present in TeamTrack alpha 2000-09-25.
In the TeamTrack alpha 2000-09-25, if I edit a Perforce filespec, the TS_TIME1 field in the filespec record in the TS_VCACTIONS table remains unchanged. This indicates to the replicator that the record is up to date with Perforce (see <URL: http://info.ravenbrook.com/project/p4d...ign/teamtrack-p4dti-schema/#section-3.2>). But the record is not up to date since it has just been changed.
Fixed in TeamTrack build 4402. GDR 2000-11-09.
How foundmanual_test
Evidence<URL: http://info.ravenbrook.com/mail/2000/10/06/13-18-13/0.txt>
Created byGareth Rees
Created on2000-10-06 14:17:39
Last modified byGareth Rees
Last modified on2001-12-10 18:55:46
History2000-10-06 GDR Created based on <URL: http://info.ravenbrook.com/mail/2000/10/06/13-18-13/0.txt>.
2000-11-09 GDR Closed.


Change Effect Date User Description
5522 closed 2000-12-06 11:14:03 Richard Brooksby Explaining the supported platforms in the readme and the FAQ.
2937 open 2000-10-09 16:39:23 Gareth Rees In replicator.changed_jobs, select even jobs that have been changed most recently by the replicator (this is a temporary workaround for job000014).
In replicator.replicate_issue_to_job, report if filespecs are changed.
In dt_teamtrack.teamtrack_filespec class, keep self.data up to date so that the filespec name can be accurately reported by looking in self.data['filespec'].