|Title||Deleting records gives the replicator a headache|
|Assigned user||Nick Barnes|
|Description||The replicator doesn't cope well when a defect tracker record is deleted. When you delete an issue, then the next time (and every subsequent time) you edit the corresponding job it will fail to fetch the issue from the DT and send e-mail to the administrator. This is not very important for the Bugzilla integration because Bugzilla does not support the deletion of bugs.|
|Analysis||When you delete a job it tries to replicate it to the issue (because it's changed) and that's likely to violate a rule in the DT, but even worse, it might succeed. RB 2000-12-04.|
In fact, that's not the case. When you delete a job, the replicator ignores the deletion. The next time someone edit the issue, it restores the job from the issue. GDR 2000-12-04.
If a Perforce job is deleted, re-create it from the DT record.
What should we do if the DT record is deleted?
See also <
GDR 2001-07-17: When an issue is deleted, then the next time the job is replicated we should (1) send an e-mail and (2) mark the job as not being replicated so that at least this doesn't keep coming up.
If we have migration all set up then we could restore the issue from the job... but this might be really annoying, like a game of Whack-a-mole. It might be better instead to set P4DTI-issue-id to "deleted" or (not so good) set P4DTI-rid to "not_replicated" or whatever.
|Created by||Richard Brooksby|
|Created on||2000-11-23 14:42:59|
|Last modified by||Nick Barnes|
|Last modified on||2018-07-05 17:26:21|
|History||2000-11-23 RB Created from e-mail discussion.|
2000-12-04 RB Improved description for end users.
2000-12-04 GDR Corrected description of what happens when a job is deleted.
2000-12-05 RB Added reference to analysis in GDR's e-mail.
2003-05-19 NB Downgrade to "optional" because Bugzilla doesn't support deletion of bugs.
2018-07-05 NB Suspended