P4DTI issue job000201

TitleEmpty assigned_to field can't be replicated (unreproducible)
Statussuspended
Prioritynice
Assigned userNick Barnes
OrganizationRavenbrook
DescriptionIf 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.
AnalysisIn configure_bugzilla.py, the "Assigned_To" field is made "required" in the Perforce jobspec. If it were optional, then this would work.
See also <http://www.ravenbrook.com/project/p4dt...2001-02-22/version-1.0-support/#job-201>.
How foundmanual_test
Evidence<http://www.ravenbrook.com/project/p4dt...c/2001-01-29/release-0.5.1-test-report/>, item 5.
Observed in0.5.1
Introduced in0.5.0
Created byGareth Rees
Created on2001-02-13 15:21:14
Last modified byNick Barnes
Last modified on2018-07-05 17:27:29
History2001-02-13 GDR Created.
2003-05-19 NB Updated to show unreproducible status.
       2018-07-05 NB Suspended because the P4DTI is obsolete.
Support

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:

The replicator failed to poll successfully, because of the following problem:

Exception:
Perforce error: Error in job specification. Missing required field 'Assigned_To'.

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.