| Title | It's hard to force the replication of particular items to the defect tracker |
| Status | suspended |
| Priority | optional |
| Assigned user | Nick Barnes |
| Organization | Ravenbrook |
| Description | It is possible for a defect tracker database to get corrupted. In that instance, administrators may want to force the replication of particular jobs, changelists, or fix records from Perforce to the defect tracker. At present we don't provide any mechanism for doing this. |
| Analysis | Could have a script, like refresh.py, for this purpose. It could have a mode in which it ensures that _all_ necessary records are in the defect tracker. |
| How found | customer |
| Evidence | http://info.ravenbrook.com/mail/2002/05/02/18-59-47/0.txt |
| Observed in | 1.2.1 |
| Introduced in | 0.3.0 |
| Created by | Nick Barnes |
| Created on | 2002-05-03 13:04:37 |
| Last modified by | Nick Barnes |
| Last modified on | 2018-07-05 17:28:03 |
| History | 2002-05-03 NB Created. 2018-07-05 NB Suspended because the P4DTI is obsolete. |