| Title | Bugzilla comments can get wrong timestamp |
| Status | suspended |
| Priority | optional |
| Assigned user | Nick Barnes |
| Organization | Ravenbrook |
| Description | If a Perforce user adds to a job description which is replicated to a Bugzilla 'longdesc' field, then the replicator replicates the additions to Bugzilla with a timestamp. This timestamp is the time at which that replication is performed, not the timestamp of the job. If the change is made while the replicator is down, and replicated when the replicator is restarted some time later, the difference can be significant. |
| Analysis | In update_longdesc() in bugzilla.py, get a better timestamp from the bug record (i.e. from the Perforce object representing the bug, which also contains information about the Perforce job) if possible. |
| How found | inspection |
| Evidence | Reading the code on 1.1 tip. |
| Observed in | 1.1.1 |
| Introduced in | 1.0.0 |
| Created by | Nick Barnes |
| Created on | 2001-07-08 21:21:45 |
| Last modified by | Nick Barnes |
| Last modified on | 2018-07-05 17:27:40 |
| History | 2001-07-08 NB Created. 2003-05-19 NB Updated. 2018-07-05 NB Suspended because the P4DTI is obsolete. |