|Title||New jobs in Perforce don't get replicated to the defect tracker|
|Assigned user||Gareth Rees|
|Description||New jobs in Perforce don't get replicated to the defect tracker.|
|Analysis||There's no design or implementation for replicating new jobs in Perforce.|
Such a design should be similar to the design for replicating new cases: look at changed jobs that have P4DTI-rid: None, see if they match some criteria, and if so, start replicating. Starting to replicate is tricky, because TeamTrack applies more stringent checks to new cases than Perforce does. In the sample workflow, for example, you have to provide values for the TITLE, SEVERITY, PROJECT and ISSUETYPE fields. It may be possible in general to deduce what these should be. (But I suppose it's up to the organization to sort out that kind of thing.)
GDR 2001-05-01: See job000022 (migration) for some analysis of the difficulties involved, and some design suggestions.
|Created by||Gareth Rees|
|Created on||2000-10-20 15:47:49|
|Last modified by||Gareth Rees|
|Last modified on||2001-12-10 18:59:55|
|History||2000-10-20 GDR Created from personal to-do list.|
2000-11-21 RB Downgraded to optional.
2001-05-01 GDR Added reference to job000022.
|24042||closed||2001-11-20 16:20:35||Gareth Rees||New manual "Advanced Administrator's Guide" (AAG).
Added new manual to build procedure and indexes.
Renamed "pre_migrate_issue" as "translate_jobspec_advanced".