P4DTI issue job000410

TitleCan't confirm an unconfirmed Bugzilla bug from Perforce
Assigned userNick Barnes
DescriptionTrying to change a Bugzilla bug from UNCONFIRMED to another state by changing the status of the corresponding Perforce job causes an error.
Here is the error:
Job 'bug27' could not be replicated to issue '27': Bugzilla database error: (P4DTI-1273) Bugzilla's fielddefs table does not include 'everconfirmed'.
AnalysisBugzilla has "UNCONFIRMED" bugs. The P4DTI is smart enough to know that a transition from UNCONFIRMED to another status has to set the 'everconfirmed' flag, but is not smart enough to know that changes to this flag are not recorded in the bugs_activity table, and therefore this field does not appear in the fielddefs table (which exists to support the bugs_activity table; see the Bugzilla schema <http://info.ravenbrook.com/project/p4dti/master/design/bugzilla-schema/> for details).
  This was previously masked by job000262, in which bugs could not be confirmed for another reason.
If the Bugzilla interface can't find a field in the fielddefs table, it should just stop trying to add it to bugs_activity. There are other such fields. The whole set is currently {assignee_accessible, cclist_accessible, creation_ts, everconfirmed, lastdiffed, qacontact_accessible, reporter_accessible}.
How foundmanual_test
EvidenceNoticed while testing 1.2.0.
Observed in1.2.0
Introduced in0.5.0
Test procedure<http://www.ravenbrook.com/project/p4dti/master/test/test_p4dti.py>, section 14
Created byNick Barnes
Created on2001-10-19 15:49:21
Last modified byNick Barnes
Last modified on2002-04-09 11:37:00
History2001-10-19 NB Created.

Advice for all releases.


Change Effect Date User Description
23568 closed 2001-10-26 13:52:37 Nick Barnes Only attempt to record a change to a Bugzilla field in bugs_activity and p4dti_bugs_activity if the field has a fieldid (in the fielddefs table).