Red Hat Bugzilla – Bug 1274777
Changing subcomponent does not reset default assignee
Last modified: 2016-01-12 00:01:21 EST
After the last bugzilla update, changing of the subcomponent (keeping the component intact) does not automatically check the "Reset Assignee to default for component" checkbox (and QA Contact and docs Contact).
This is very inconvenient, as we deal with misreported bugs quite often and switching to a different subcomponent is now prone to mistakes.
As this worked before and still works when changing components, I suppose it's a bug introduced by the latest update.
This bug indeed exist in qe environment, qe will add case to cover this scenario.
Verified this issue.
The result is PASS
Change one bug's subcomponent and save.
Result: The "Reset Assignee to default for component" will be checked and the default assignee, QA and Doc contact are set correctly.
Thanks a lot for the quick fix. Do you have an ETA when it is going to be deployed to bugzilla.redhat.com? The bug is quite irritating and we hit it several times each day. Thanks!
(In reply to Jiri Benc from comment #3)
> Thanks a lot for the quick fix. Do you have an ETA when it is going to be
> deployed to bugzilla.redhat.com? The bug is quite irritating and we hit it
> several times each day. Thanks!
We are aiming for an early to mid December release.
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.