P4DTI issue job000036

TitleNew jobs in Perforce don't get replicated to the defect tracker
Assigned userGareth Rees
DescriptionNew jobs in Perforce don't get replicated to the defect tracker.
AnalysisThere'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.
How foundinspection
EvidenceSee migrate_teamtrack.py.
Observed in0.3.2
Test procedure<http://www.ravenbrook.com/project/p4dti/master/test/test_p4dti.py>, section 15
Created byGareth Rees
Created on2000-10-20 15:47:49
Last modified byGareth Rees
Last modified on2001-12-10 18:59:55
History2000-10-20 GDR Created from personal to-do list.
2000-11-21 RB Downgraded to optional.
2001-05-01 GDR Added reference to job000022.


Change Effect Date User Description
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".