| Title | Bad names for custom fields |
| Status | closed |
| Priority | essential |
| Assigned user | Nick Barnes |
| Organization | Ravenbrook |
| Description | When replicating Bugzilla custom fields, we need to get a meaningful field name for the jobspec. We should use the field's "Description" (from the Bugzilla database), modified if necessary to make it acceptable as a Perforce job field name. |
| Analysis | Use fielddefs.description, and use the keyword_translator to encode bad characters. |
| How found | manual_test |
| Evidence | I just know |
| Observed in | 2.3.5 |
| Created by | Nick Barnes |
| Created on | 2007-07-30 09:22:06 |
| Last modified by | Nick Barnes |
| Last modified on | 2007-07-30 09:23:09 |
| History | 2007-07-29 NB Created. |
| Change | Effect | Date | User | Description |
|---|---|---|---|---|
| 162997 | closed | 2007-07-29 16:28:18 | Nick Barnes | Support custom fields with special characters in their names. |
| 162691 | closed | 2007-06-29 13:57:30 | Nick Barnes | Pick up custom field names from database. |