Closed Bug 667903 Opened 13 years ago Closed 13 years ago

Advanced search UI issue in Bugzilla 4.0.1

Categories

(Bugzilla :: Query/Bug List, defect)

4.0.1
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 622487

People

(Reporter: dorusinec, Unassigned)

Details

Bugzilla 4.0.1

Browsers:
Google Chrome 12.0.742.100
IE 9.0.8112.16421

OS: Windows 7 x86

After selecting the product in Advanced Search, some fields (component, version, target milestone) do not fit with product real values and are selected from next product.

Preconditions:
1. In Bugzilla version 3.6 create for example 3 products (Product1, Product2, Product3). For each product create few components, versions and target milestones.

2. Upgrade Bugzilla version 3.6 to version 4.0.1

Initial state:
Upgrade to Bugzilla version 4.0.1 is successfully done.

Steps for repeating:
1. open advanced search

2. Products are sorted in field Product in this order:
   Product1
   Product2
   Product3

3. Click on Product1 and you will see that component, version, target milestone are showed from Product2.
   Click on Product2 and you will see that component, version, target milestone are showed from Product3.

Problem:
There is problem that components, versions, target milestones are not shown correctly for the products in Advanced Search. Therefore is Advanced Search useless for us.

Expected behaviour:
Components, versions, target milestones should be shown correctly for the products in Advanced Search.

We had not problem with Advanced search in Bugzilla 3.6, but after upgrade to Bugzilla 4.0.1 we have a problem mentioned above.

Repeatability: 100%
It looks like one of your products (maybe Product 1) doesn't have any component, version or target milestone. If that's the case, then this explains the problem you get.
Assignee: ui → query-and-buglist
Component: User Interface → Query/Bug List
OS: Windows 7 → All
Hardware: x86 → All
In case my guess is correct, then that's a duplicate of bug 622487.
(In reply to comment #1)
> It looks like one of your products (maybe Product 1) doesn't have any
> component, version or target milestone. If that's the case, then this
> explains the problem you get.

Yes, one of our product hadn't any component. Now it works fine.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.