Change Columns during Advanced Search doesn't always work

RESOLVED INVALID

Status

()

RESOLVED INVALID
14 years ago
14 years ago

People

(Reporter: aditya_palande, Unassigned)

Tracking

2.18
x86
Windows 2000

Details

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)
Build Identifier: 

In bugzilla, if one goes to "Advanced Search" link and does some combination of 
search. Later, one wants to "Change Columns" so that one can get some more data 
in the report. If we select "Build Found" or "Build Fixed", the report does not 
give this data.

Reproducible: Always

Steps to Reproduce:
1. as per detailed description
2.
3.

Actual Results:  
The report doesn't include the extra columns requested

Expected Results:  
Should have shown those extra columns

Comment 1

14 years ago
I see no "Build Found" or "Build Fixed" anywhere in Bugzilla. Is that a local
customization on your Bugzilla?

What version are you using?
(Reporter)

Comment 2

14 years ago
"Build Found" and "Build Fixed" are custom fields within our installation. 
Perhaps custom fields do not share the same default functionality as standard 
fields within bugzilla?

Basically, this is what happens: Say we provide some combination of search 
parameters in Advanced Search, then go to the "change columns" link at the 
bottom. In this, we can check the checkbox besides "Build Fixed" or other 
custom fields, and resubmit the page by clicking on the button that 
says "Change Columns". This change does not appear in the new page after submit.
Version: unspecified → 2.18

Comment 3

14 years ago
Yeah, that's a problem with a bug in your local customizations. Bugzilla doesn't
natively support custom fields, yet.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → INVALID

Comment 4

14 years ago
Oh, by the way, though, if you'd like some support help with your
customizations, you can see the resources available at
http://www.bugzilla.org/support/
You need to log in before you can comment on or make changes to this bug.