Bug 1136687

Summary:	show_bug.cgi: Component list doesn't change type when changing product
Product:	[Community] Bugzilla	Reporter:	Jason McDonald <jmcdonal>
Component:	Creating/Changing Bugs	Assignee:	PnT DevOps Devs <hss-ied-bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:	tools-bugs <tools-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.4	CC:	jmcdonal, mtyson, qgong, tools-bugs
Target Milestone:	4.4
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-09-20 23:29:58 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jason McDonald 2014-09-03 05:20:48 UTC

Description of problem:
Red Hat Bugzilla has different types for the Component field, depending on the selected product and it's settings.

For example, a product which allows multiple components to be selected for a bug presents a listbox, while a product that only allows a single component to be selected for a bug has a drop-down list.

When moving a bug between products where the type differs, the Component field does not change type. For example, if I attempt to reassign a bug from a product which allows one component per bug to a product that allows multiple components per bug, the Component field stays as a drop-down list and I can't select multiple components without going to the next page.

The converse is also true; if I move a bug from a product that allows multiple components to one that doesn't, the Component list stays as a list-box and allows multiple components to be selected. All but one component is discarded when I go to the next screen.

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

How reproducible:
Always

Steps to Reproduce:
1. Scroll up and observe that the component field of this bug is a drop-down list.
2. Change the product from "Bugzilla" to "JBoss Enterprise Web Server 2". (that product allows multiple components per bug.)
3. Observe that the Component field remains as a drop-down list and only one component can be selected.

Actual results:
The contents of the Component list change to the correct ones for the new product, but the list is still a drop-down and only one component can be selected.

Expected results:
Component field changes from a drop-down to a list-box, and allows multiple components to be selected.

Additional info:
none

Comment 1 Rony Gong 🔥 2015-05-20 08:02:13 UTC

Retest this bug in build 4.4.9033-5
1. Scroll up and observe that the component field of this bug is a drop-down list.
2. Change the product from "Bugzilla" to "JBoss Enterprise Web Server 2". (that product allows multiple components per bug.)
3. Change the product from "Bugzilla" to "Beaker". (that product not allows multiple components per bug.)

Both step 2 and step3's result is:
Component field changes from a drop-down to a list-box, and allows multiple components to be selected.

But step3 will show deny error page when select multi components and click save button.

Comment 2 Jeff Fearn 🐞 2015-06-10 06:42:32 UTC

I can't duplicate this, does it still happen post sprint 34?

Comment 3 Rony Gong 🔥 2015-06-10 07:19:48 UTC

QE test this again in the latest build(4.4.9034-5), only below issue seems need to be fix:
Steps:
1.Open a bug which doesn't support multiple components, like bugzilla
2.Then change this bug's product to another product which doesn't suppot multiple components neither, like beaker
3.Check the component select box
Actual results:
It could input multiple components

Expected results:
It should forbidden multiple component input

Comment 5 Jeff Fearn 🐞 2015-07-22 21:57:45 UTC

Hi Rony, this seems to work fine on 4.4.9037-5

Comment 6 Rony Gong 🔥 2015-07-23 02:09:35 UTC

It fixed in 4.4.9037-5, but filed a new bug 1245861 when testing this bug.

Comment 7 Matt Tyson 🤬 2015-09-20 23:29:58 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.