Red Hat Bugzilla – Bug 1296697
"Change several bugs at once" will erroneously reset the QA Contact field to its default
Last modified: 2016-06-05 20:41:15 EDT
Description of problem:
When using "Change several bugs at once", selecting one or more bzs to be changed, modifying the Subcomponent field while leaving the "QA Contact"
field alone (so it stays "do-not-change"), the QA Contact field will revert back to the default value.
Not sure if this is exclusive to the Subcomponent and QA Contact fields or if other field changes will effect QA Contact OR other fields will be reset to default in addition to QA Contact but I have been annoying my QE counterpart by making modifications to fields and I would like to stop being annoying.
Version-Release number of selected component (if applicable):
Bugzilla version 4.4.11045.3
Seems to happen all the time.
Steps to Reproduce:
"do-no-change" is not adhered.
A field that is "do-not-change" should remain unchanged.
For an example, these 8 bugs were changed by "Change several bugs at once" yesterday when moving the state from NEW to ASSIGNED, and both the Assignee and QA Contact were reset to default values (which was not desired).
I discussed this bug with John Shortt yesterday. There has been a regression at some point where the "Reset Assignee to Default" checkbox is now checked by default instead of clear. (The same is true for hte QA contact and Docs Contact checkboxes.)
Every field on the bulk-change form should default to "-do-not-change-", so the checkboxes should be clear by default.
We first noticed this bug in mid-December , if that helps to narrow down when the regression was introduced, possibly with the upgrade to 4.4.10045.3 on Dec 15 .
Someone else just trundled into this with 15-20 bugzillas. Took out the Assigned To field in addition to the QA field. Very time consuming to put back the correct values. Please fix as soon as possible. Thanks.
Another batch of 34 kernel-aarch64 bugs just had their Assignee and QA Contacts reset to default values. Please fix this bug soon since it's not easy to undo these mass updates.
Yeah, that's really bad. Sorry about that.
I'm organizing a hotfix for this issue.
Rdu environment with version(4.4.11045-4, DB: psql)
1.Search a bug list, then click link 'Change Several Bugs at Once', then select some bugs in the new page
==>"Reset Assignee to Default" checkbox is now unchecked by default
==>"Reset QA to Default" checkbox is now unchecked by default
==>"Reset Docs Contact to Default" checkbox is now unchecked by default
2.Select new product, component and subcomponent
==>"Reset Assignee to Default" checkbox is still unchecked by default
==>"Reset QA to Default" checkbox is still unchecked by default
==>"Reset Docs Contact to Default" checkbox is still unchecked by default
==>all selected bug's role not changed, same as before.
4. Also check the output of check that 3 checkbox manually
==>all selected bug's role changed to the component/subcomonent's default setting.
*** Bug 1297909 has been marked as a duplicate of this bug. ***
*** Bug 1298602 has been marked as a duplicate of this bug. ***
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.