644634 - product field for multiple projects that need common components.

Status: RESOLVED DUPLICATE of bug 120248

(Bugzilla :: Bugzilla-General, enhancement)

Description

[shassell]

User-Agent:       Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; GTB6.6; InfoPath.2; .NET CLR 2.0.50727; MS-RTC LM 8; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET4.0C; .NET4.0E)
Build Identifier: 3.4.8

Currently the product is the unique identifier and the component set is tied to the product.  Since we have multiple products/projects that the same components with 3.4.8 we have to entere in the component set each time a new project is created. 

Would like for the components to not be tied to product/project if possible so that that the component list could be entered in once when a new product/project is created the ability to select from the common component list to identify the components associated with the product/project.

Reproducible: Always

Steps to Reproduce:
1. Add New product
2. In the Add New product, you have to entere in components and do so you have to add the components, you can't select from an existing component list.
 
Actual Results:  
See above.

Expected Results:  
Would like the be able to select tmultiple components associated with a project/product from a list.

Comment 2

[:glob ✱]

actually bug 120248 is a better match for this request.

Comment 3

[shassell]

It's not clear that this is a duplicate?

Basically current release makes the following happen:

Project A
   Add component A
   Add component .
   Add component n

Project B
   Add component A
   Add component .
   Add component n

.

Project N
   Add component A
   Add component .
   Add component n

----

Instead would like to see:

Add component A
Add component .
Add component n
Save component list


Add project A
    Select components from saved component lsit
Add project .
    Select components from saved component list
Add project n
    Select components from saved component list

Comment 4

[Max Kanat-Alexander]

It's clearer with bug 120248.

Also, note that in 4.0 you could do this with a custom field.