Open
Bug 656239
Opened 13 years ago
Updated 13 years ago
Selection of field from section "selected columns" doesn't disapear when you add some ather field to "selected columns" section
Categories
(Bugzilla :: Query/Bug List, defect)
Bugzilla
Query/Bug List
Tracking
()
NEW
People
(Reporter: stasyasin, Unassigned)
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; InfoPath.2; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729) Build Identifier: Selection of field from section "selected columns" doesn't disapear when you add some ather field to "selected columns" section Reproducible: Always Steps to Reproduce: Steps to reproduce: 1) log in Bugzilla 2) Do any search that returns several bugs 3) Click on "Change columns" link from result set. 4) Select some filed ( in example "Target") from "Available columns" section and click on "->" button 5) Several times click on "^" up button from "selected columns" section 6) Select some other field (in example "Keyword") from "Available columns" section and click on "->" button 7) Click on "^" up button from "selected columns" section Actual Results: Fields that you select in step 4 and in step 6 will be moved up Expected Results: Only Keyword filed ( filed that you selected from step 6) will be moved up
Comment 1•13 years ago
|
||
Reproduced, but I'm not sure this is a bug. Mozilla/5.0 (X11; Linux x86_64; rv:5.0a2) Gecko/20110513 Firefox/5.0a2 The Product of this alleged bug should probably be changed to Bugzilla or bugzilla.mozilla.org depending on if this is considered to be a program or site specific issue.
Updated•13 years ago
|
Assignee: nobody → general
Component: Preferences → Bugzilla-General
Product: Firefox → Bugzilla
QA Contact: preferences → default-qa
![]() |
||
Updated•13 years ago
|
Assignee: general → query-and-buglist
Status: UNCONFIRMED → NEW
Component: Bugzilla-General → Query/Bug List
Ever confirmed: true
OS: Windows XP → All
Hardware: x86 → All
You need to log in
before you can comment on or make changes to this bug.
Description
•