575501 - Custom field doesn't appear when a field it's dependent on appears with a default value

Status: RESOLVED DUPLICATE of bug 520993

(Bugzilla :: Creating/Changing Bugs, defect)

Description

[Frank Tzanabetis]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 (.NET CLR 3.5.30729)
Build Identifier: 3.4.5

If a custom field is dependent on the Resolution field being set to "FIXED" (default value), it wont appear when the resolution field appears when the status field is set

Reproducible: Always

Steps to Reproduce:
1. Ensure that the default value for "Resolution" is "FIXED"
2. Create a custom field
3. Set the custom field's "Field only appears when" property to "Resolution (resolution)"
4. Set "is set to" to "FIXED" (which is the default value).
5. Open an existing bug
6. Set the Status field to "RESOLVED"

Actual Results:  
The "Resolution" field appears with the default value of "FIXED", but the custom field is still invisible.

Expected Results:  
The custom field should appear when the resolution field appears with "FIXED".

A further step - 

7. Set the "Resolution" field to something else, and then back to "FIXED"
  -- The custom field appears as expected.

Comment 1

[Max Kanat-Alexander]

  Thanks for the report! I think this was fixed in a later release than the one you are using, but I'm not certain. Also, I don't remember off the top of my head what the bug number was.

Comment 2

[Frédéric Buclin]

Fixed in 3.4.6.

Comment 3

[Frank Tzanabetis]

Bah!  Sorry, my bad.  I searched high and low to see if it was reported already too...