Bug 1274777 - Changing subcomponent does not reset default assignee
Summary: Changing subcomponent does not reset default assignee
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Creating/Changing Bugs
Version: 4.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: 4.4
Assignee: PnT DevOps Devs
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-23 13:58 UTC by Jiri Benc
Modified: 2018-12-09 06:29 UTC (History)
7 users (show)

Fixed In Version: 4.4.10045.3
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-16 02:14:09 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1296697 0 high CLOSED "Change several bugs at once" will erroneously reset the QA Contact field to its default 2021-02-22 00:41:40 UTC

Internal Links: 1296697

Description Jiri Benc 2015-10-23 13:58:03 UTC
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.

Comment 1 Rony Gong 🔥 2015-10-26 01:43:02 UTC
This bug indeed exist in qe environment, qe will add case to cover this scenario.

Comment 2 Hui Wang 2015-11-11 08:24:09 UTC
Verified this issue.
The result is PASS
Version:
rh-bugzilla-4.4.10044-1.el6.noarch
Steps: 
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.

Comment 3 Jiri Benc 2015-11-23 11:50:42 UTC
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!

Comment 4 Muhammad Tahir 2015-11-23 22:52:04 UTC
(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.
Thanks.

Comment 5 Matt Tyson 🤬 2015-12-16 02:14:09 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.