P4DTI issue job000233

TitleWhen you submit a new issue to TeamTrack it overwrites the issue
Assigned userGareth Rees
DescriptionWhen you submit a new issue in TeamTrack, then the replicator sets up that issue for replication and replicates it to Perforce. Then the next time it polls, it thinks that the issue and the corresponding job have changed, so it overwrites the jobs with the issue.
This also happens when you run the replicator for the first time, if there are issues modified since the start_date. All the issues get replicated and then overwritten.
AnalysisThe reason for this is that the issue has indeed changed (by the replicator setting the P4DTI_* fields for the issue). The problem is that the replicator has set those fields using TSServer::UpdateRecord, not TSServer::Transition, so the TS_REALUSERID field is 0 in the records in the TS_CHANGES table, so the replicator thinks that someone else has made those changes.
This can be fixed by adjusting the query in dt_teamtrack.changed_entities so that it ignores changes with T_USERID=<the replicator> and TS_REALUSERID=0.
How foundmanual_test
Evidence<http://www.ravenbrook.com/project/p4dt...2001-02-26/release-1.0.1-test-report-3/>, item 2.
Observed in1.0.1
Introduced in1.0.0
Test procedure<http://www.ravenbrook.com/project/p4dti/master/test/test_p4dti.py>, section 10
Created byGareth Rees
Created on2001-02-27 16:52:43
Last modified byGareth Rees
Last modified on2001-12-10 19:26:30
History2001-02-27 GDR Created.


Change Effect Date User Description
9162 closed 2001-02-27 17:09:50 Gareth Rees The dt_teamtrack.changed_entities method ignores changes with TS_USERID=<self> as well as changes with TS_REALUSERID=<self>, so as to get the correct set of changed issues.