Ravenbrook / Projects / Perforce Defect Tracking Integration / Issues
Perforce Defect Tracking Integration
| Title: | Logical field name "code" not allowed in TeamTrack |
| Status: | closed |
| Priority: | nice |
| Assigned user: | gdr |
| Product: | p4dti |
| Organization: | Ravenbrook |
| Description: | We can't allow a field whose logical field name is "code" in TeamTrack because Perforce uses the Python key "code" to return status information. |
| Analysis: | We detect and complain about it in "//info.ravenbrook.com/project/p4dti/version/0.4/code/replicator/configure_teamtrack.py#1" but we could map TeamTrack "code" to "_code" or something, like we do with TeamTrack states called "new". RB 2000-12-06 Logical field names in TeamTrack generally have mixed case, and anyway can be changed so this is not worth having a special case for in the configuration generator. Instead, document it in the AG. GDR 2000-12-08 |
| How found: | inspection |
| Evidence: | "//info.ravenbrook.com/project/p4dti/version/0.4/code/replicator/configure_teamtrack.py#1" line 260 |
| Observed in: | 0.4 |
| Introduced in: | 0.0.0 |
| Test procedure: | <http://www.ravenbrook.com/project/p4dti/master/test/test_p4dti.py>, section 6.3 |
| Created by: | Richard Brooksby |
| Created on: | 2000-12-07 13:12:01 |
| Last modified by: | gdr |
| Last modified on: | 2001-12-10 19:12:52 |
| History: | 2000-12-06 RB Created. 2000-12-08 GDR Corrected title and description. |
| Change | Effect | Date | User | Description |
|---|---|---|---|---|
| 5819 | closed | 2000-12-11 15:50:11 | gdr | Merged changes from version 0.4 back to master. |
| 5682 | closed | 2000-12-08 12:00:39 | gdr | Translate state name "ignore" to "_ignore" in configuration generators. Documented translation of "ignore" state. Improved advice about what to do with a field called "code". Fixed table of contents. |
Generated at 2008-12-01 21:24:50 by $Id: //info.ravenbrook.com/infosys/cgi/issue.cgi#430 $
Copyright © Ravenbrook Limited. This document is provided "as is", without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this document. You may make and distribute verbatim copies of this document provided that you do not charge a fee for this document or for its distribution.