|Title||Empty assigned_to field can't be replicated (unreproducible)|
|Assigned user||Nick Barnes|
|Description||If the "Assigned to" field in Bugzilla is empty, then it can't be replicated. You get the error "Error in job specification. Missing required field 'Assigned_To'." Ravenbrook has been unable to reproduce this problem.|
We haven't been able to make a bug with an empty "assigned to" field (if you don't fill it in it gets set to the owner of the component, and in any case the assigned_to column is required to be NOT NULL in the underlying database schema). However, it was seen in beta testing.
|Analysis||In configure_bugzilla.py, the "Assigned_To" field is made "required" in the Perforce jobspec. If it were optional, then this would work.|
See also <
|Created by||Gareth Rees|
|Created on||2001-02-13 15:21:14|
|Last modified by||Nick Barnes|
|Last modified on||2018-07-05 17:27:29|
|History||2001-02-13 GDR Created.|
2003-05-19 NB Updated to show unreproducible status.
2018-07-05 NB Suspended because the P4DTI is obsolete.
Advice for all releases.
Symptom. This happens only in the Bugzilla integration. The integration administrator receives a sequence of automatically generated e-mails from the replicator that look like this:
Cause. The "Assigned_To" field has become empty in Bugzilla; we believe that this can't happen in Bugzilla 2.10, so that's why it causes an error in the replicator. So this can only happen at a site which is not running Bugzilla 2.10, or which has changed the way Bugzilla 2.10 works, or where someone has edited the Bugzilla database directly, bypassing Bugzilla.
Workaround. Assign the bug to someone in Bugzilla.
If you're sure that you're running a vanilla Bugzilla 2.10, then please try to work out how the "Assigned_To" field became empty and report this to Ravenbrook so that we can fix the problem.