Custom field value visibility by Status or Resolution does not work




User Interface
8 years ago
7 years ago


(Reporter: Liya, Unassigned)



(Whiteboard: [3.6 only; 4.0 and tip not affected])



8 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 GTB6
Build Identifier: 

Custom field value visibility by Status or Resolution does not work

Reproducible: Always

Steps to Reproduce:
1. Create a custom field (Drop Down or Multi-Selection Box), define values visibility by Status.
2. Add legal values for your new field while add a visibility at least for some of them to a specific Status value, for example - RESOLVED
3. Open existing bug, change its status to RESOLVED
Actual Results:  
the list of the values in your custom field does not change

Expected Results:  
Values that are defined to be visible for RESOLVED status should appear in the list

- same flow can be reproduced for Resolution
- no JS errors..

Comment 1

8 years ago
Looks like a dupe of bug 520993. Which version of Bugzilla do you have?

Comment 2

8 years ago
I have the latest - Bugzilla 3.4.6
bug 520993 was about field visibility (and I opened it :)), 
this one about values visibility.

Comment 3

7 years ago
I can reproduce the issue in Bugzilla 3.4.6 and 3.6, but not in 3.7. mkanat, do you remember which bug fixed this problem?
OS: Mac OS X → All
Hardware: x86 → All
Version: unspecified → 3.4.6

Comment 4

7 years ago
Maybe fixed by bug 512606?

Comment 5

7 years ago
(In reply to comment #4)
> Maybe fixed by bug 512606?

Hum no, there has been no change in knob.html.tmpl since 3.6.

Comment 6

7 years ago
Is it possible we did a different fix on HEAD than on the branches for that bug...? Otherwise I don't know what bug would have fixed this.

Comment 7

7 years ago
Confirming for now as I can reproduce with 3.6.
Ever confirmed: true


7 years ago
Whiteboard: [3.6 only; 4.0 and tip not affected]
Target Milestone: --- → Bugzilla 3.6

Comment 8

7 years ago
I definitely don't know for sure which bug fixed this problem in 4.0 and 4.1. Maybe it could be bug 487508, but I'm really not sure. mkanat, unless you have an idea what's wrong with 3.6, I suggest we close this bug as WFM as it's fixed in newer releases.

Comment 9

7 years ago
Well, at the moment it's not fixed in any stable release, and 3.6 is our current stable series, so until 4.0 becomes the stable series, I think we should keep this open.


7 years ago
Target Milestone: Bugzilla 3.6 → Bugzilla 4.0

Comment 10

7 years ago
Status Whiteboard says this was 3.6 only, and 3.6 is locked to security fixes only now, so this should be handled now unless the Whiteboard is wrong.
Last Resolved: 7 years ago
Resolution: --- → WORKSFORME
Target Milestone: Bugzilla 4.0 → ---
You need to log in before you can comment on or make changes to this bug.