P4DTI issue job000370

TitleJournal fields in TeamTrack 5.0 can't be replicated
Assigned userGareth Rees
DescriptionIf you have a "journal" text field in TeamTrack 5.0, then when you submit an issue with such a field, the P4DTI refuses to replicate it, stopping with an error from Perforce complaining about a "Syntax error" in the job form at the line containing the text from the journal field.
AnalysisJournal fields were added in TeamTrack 5.0. They are text fields (field type 101) with TS_ATTRIBUTE = 3. The TeamTrack configuration generator doesn't recognize them as being multi-line text fields because it's looking for attribute 0. So these fields don't go through the text_translator, and so don't have a newline added to the end when translated to Perforce. And Perforce is complaining about the absence of a final newline.
Journal fields are not described in the TeamTrack database schema document. Also, we don't know what TS_ATTRIBUTE = 2 means. Perhaps this is another kind of multi-line text field.
So configure_teamtrack should probably test for attribute != 1 rather than attribute = 0 as it does at present.
It would be nice to have a test case for this.
How foundmanual_test
Evidence<http://www.ravenbrook.com/project/p4dti/doc/201-07-24/release-1.1.3-test-report/>, item 10.
Observed in1.1.3
Introduced in1.1.2
Test procedure<http://www.ravenbrook.com/project/p4dti/master/test/test_p4dti.py>
Created byGareth Rees
Created on2001-07-24 15:40:02
Last modified byGareth Rees
Last modified on2001-12-10 19:52:25
History2001-07-24 GDR Created.


Change Effect Date User Description
14455 closed 2001-07-24 22:45:52 Gareth Rees Recognize TeamTrack journal fields as being multi-line text fields.