Open
Bug 622849
Opened 14 years ago
Updated 12 years ago
needless screens in browse-to for products with only one component
Categories
(Bugzilla :: Bugzilla-General, enhancement, P3)
Tracking
()
NEW
People
(Reporter: vince.skahan, Unassigned)
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Build Identifier: bugzilla 3.6.3
The 'browse' functionality forces the user through a no-value screen for the case where a particular product has only 'one' component defined.
Reproducible: Always
Steps to Reproduce:
1. create a new product
2. define only one component (ie, 'all') for that product
3. enter a ticket for that product
4. use the main menu 'browse' pick, select that product
Actual Results:
The user is presented with a screen requesting they select a component for that product being browsed. There is only one component there (ie, the user is forced to click-through a no-value-added screen)
Expected Results:
User should not have been presented with the 'select a component' screen. For products with only one component, the component should have been auto-selected and the user should not have been presented with that screen at all.
google groups discussion thread is at http://groups.google.com/group/mozilla.support.bugzilla/browse_thread/thread/d14d393e55321f49#
![]() |
||
Comment 1•14 years ago
|
||
The page which displays components brings some value even with a single component. It displays the description of the component, its default assignee and QA contact. IMO, we shouldn't skip this page.
Severity: normal → enhancement
OS: Linux → All
Hardware: x86 → All
Version: unspecified → 3.6.3
Comment 2•14 years ago
|
||
The intermediate page is useful when you are trying to describe components, but not when you are trying to browse. (Unfortunately there isn't currently a way to tell what you are doing, but we could work out some way, possibly.)
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•14 years ago
|
Priority: -- → P3
You need to log in
before you can comment on or make changes to this bug.
Description
•