Closed Bug 287186 Opened 20 years ago Closed 20 years ago

Bug list change columns functionality does not do anything

Categories

(Bugzilla :: Query/Bug List, defect)

2.18
x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: jean-christian.imbeault, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)

When I try and change the coulms displayed by using the "Change Columns" link
(bugzilla/colchange.cgi) no matter what columns I check as wanting, the columns
displayed are always the same.

Reproducible: Always

Steps to Reproduce:
1. Click Search Bugs link
2. Leave defaults of Open, All, no keywords
3. Click Search
4. Scroll to bottom of page and click "Change Columns" link
5. Check an unchecked check box
6. Click on the "Change Columns" button

Actual Results:  
The same list as displayed after step 3 comes up. The new columns is not displayed.

Expected Results:  
A new columns should could up in the displayed results

Clicking on the "Stagger Headers" radio button doe snot do anything either.
What version of Bugzilla, and what webserver is it running on?
and by what webserver I mean Apache, IIS, etc.
Bugzilla 2.18
Server version: Apache/1.3.31 (Unix)
Version: unspecified → 2.18
In case it's useful I also have these cookies (among other) set:

COLUMNLIST: 
PATH: /
changeddate%20bug_severity%20priority%20assigned_to_realname%20bug_status%20resolution%20component%20short_short_desc

COLUMNLIST: 
PATH: /bugzilla/
bug_severity%20priority%20assigned_to_realname%20bug_status%20resolution%20component%20short_short_desc

BUGLIST: 52%3A165

I don't know why but I seemn to have two COLUMNLIST cookies. I'll delete both
and see what happens.
Deleting the two cookies fixed it. Don't know how I ended up with two cookies
... maybe during my upgrade from rc3?

Sorry to waste your time.
No problem, that is a common thing to run into with an upgrade if you haven't
set cookiepath either before or after the upgrade, or at some point when testing.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.