|Title||Edited filespecs aren't replicated from TeamTrack to Perforce|
|Assigned user||Gareth Rees|
|Description||When 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.|
|Analysis||This 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:
Fixed in TeamTrack build 4402. GDR 2000-11-09.
|Created by||Gareth Rees|
|Created on||2000-10-06 14:17:39|
|Last modified by||Gareth Rees|
|Last modified on||2001-12-10 18:55:46|
|History||2000-10-06 GDR Created based on <URL: |
2000-11-09 GDR Closed.
|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'].