|Title||new jobs break TeamTrack integration if LASTMODIFIEDDATE or SUBMITDATE are replicated|
|Assigned user||Nick Barnes|
|Description||In the TeamTrack integration, if either of the fields LASTMODIFIEDDATE and SUBMITDATE are replicated (i.e. are in the replicated_fields configuration parameter) and the P4DTI is set up to replicate new jobs (i.e. replicate_job_p is defined to return 1), and a new job is created without filling in these fields, the P4DTI fails.|
The failure is reported like this:
2002-04-05 14:39:41 UTC (P4DTI-9082) Job 'job000007' could not be replicated to the defect tracker.
2002-04-05 14:39:41 UTC (P4DTI-9093) The replicator failed to replicate Perforce job 'job000007' to the defect tracker, because of the following problem:
2002-04-05 14:39:41 UTC (P4DTI-891X) Error (TeamShare API error): ERROR: 'Submit Date' field requires a value.
'Last Modified Date' field requires a value.
Invalid field values for submit
|Analysis||This was found while investigating job000437. The translator is putting -2 into the date slots, which is the TeamTrack code for a NULL date. But TeamTrack won't accept this when creating an issue. The solution is to extend prepare_issue_advanced so that if one of these slots has -2, it gets deleted. Then TeamTrack fills in the current date for these and the job gets updated appropriately.|
|Evidence||Found by hand-testing.|
|Created by||Nick Barnes|
|Created on||2002-04-05 16:28:21|
|Last modified by||Gareth Rees|
|Last modified on||2002-06-24 20:10:56|
|History||2002-04-05 NB Created|
|27878||closed||2002-04-05 16:35:27||Nick Barnes||Handle replication of new jobs when LASTMODIFIEDDATE or SUBMITDATE are in replicated_fields.|