Description of problem: The activity fields are trigger uninitialized value warnings. Version-Release number of selected component (if applicable): Pg How reproducible: Easy Steps to Reproduce: 1. Find a bug in the DB where added or removed are null 2. Tail the error log 3. View the bug in a b rowser Actual results: Use of uninitialized value $added in pattern match (m//) at /var/www/html/bugzilla/Bugzilla/Bug.pm line 4894. Use of uninitialized value $added in string eq at /var/www/html/bugzilla/Bugzilla/Bug.pm line 4894. Use of uninitialized value in split at /var/www/html/bugzilla/extensions/InlineHistory/Extension.pm line 120. Use of uninitialized value in string eq at /var/www/html/bugzilla/extensions/InlineHistory/Extension.pm line 80. Use of uninitialized value $removed in pattern match (m//) at /var/www/html/bugzilla/Bugzilla/Bug.pm line 4894. Expected results: No errors Additional info: The added & removed fields are NULL-able and thus must be checked for defined before they are evaluated.
QE still could get below error message when open bug 17241: Use of uninitialized value $removed in pattern match (m//) at /var/www/html/bugzilla/Bugzilla/Bug.pm line 4894. Use of uninitialized value $removed in pattern match (m//) at /var/www/html/bugzilla/Bugzilla/Bug.pm line 4894. Use of uninitialized value $added in pattern match (m//) at /var/www/html/bugzilla/Bugzilla/Bug.pm line 4894. Use of uninitialized value $removed in pattern match (m//) at /var/www/html/bugzilla/Bugzilla/Bug.pm line 4894. Use of uninitialized value in split at /var/www/html/bugzilla/extensions/BayotBase/Extension.pm line 99. Use of uninitialized value in split at /var/www/html/bugzilla/extensions/BayotBase/Extension.pm line 99
Use of uninitialized value in split at /var/www/html/bugzilla/extensions/BayotBase/Extension.pm line 99 To fix this you will need the following in the data/params file. 'bb_bug_entry_fields' => 'summary product component severity priority comment',
Tested on QA environment(bzweb01-qe) with version(4.4.9039-2, DB: mysql) QA environment(bzperfweb01.app.qa) with version(4.4.9039-2, DB: psql ) Result: Pass It will not log such kind of error when open bug 17241 @Matt, Thanks a lot for your kindly reminder of setting bb_bug_entry_fields' => 'summary product component severity priority comment',
This change is now live. If there are any issues, do not reopen this bug. Instead, you should create a new bug and reference this bug.