Bug 1136693 - show_bug.cgi: Subcomponent field does not appear when moving a bug to a new product and component
Summary: show_bug.cgi: Subcomponent field does not appear when moving a bug to a new p...
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: Jeff Fearn 🐞
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On: 1157849
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-03 05:33 UTC by Jason McDonald
Modified: 2018-12-09 06:29 UTC (History)
3 users (show)

Fixed In Version: 4.4.9039
Clone Of:
Environment:
Last Closed: 2015-09-20 23:28:55 UTC
Embargoed:


Attachments (Terms of Use)

Description Jason McDonald 2014-09-03 05:33:29 UTC
Description of problem:
If I change a bug's component to one that has subcomponents, a new drop-down appears to allow me to select a subcomponent.

However, if I change both product and component, the subcomponent field does not appear.

Version-Release number of selected component (if applicable):
4.4.5024

How reproducible:
Always

Steps to Reproduce:
1. Scroll up and change the Component field to 'Internal Tools".
2. Observe that a new "Internal Tools Sub Component" label and drop-down list appear.
3. Change the Product to "Red Hat Enterprise Linux 7" and then change the Component to "kernel".

Actual results:
The "Kernel Sub Componnet" field does not appear.

Expected results:
The "Kernel Sub Component" field appears.

Additional info:
The "Kernel Sub Component" field appears as expected if the Product was already set to Red Hat Enterprise Linux 7.

Comment 1 Rony Gong 🔥 2015-05-20 08:08:00 UTC
Retest this bug in build 4.4.9033-5
This bug couldn't be reproduced, The "Kernel Sub Componnet" field exist there.

Comment 2 Jason McDonald 2015-05-20 12:28:06 UTC
Resolved by the same patch as Bug 1157849.

Comment 3 Matt Tyson 🤬 2015-09-20 23:28:55 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.