User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:18.104.22.168) Gecko/20080404 Firefox/22.214.171.124 Build Identifier: bugzilla 3.0.4 By default in bugzilla-3.0.4 package parameters "usestatuswhiteboard" and "usebugaliases" are set up to OFF values. But in the query page in box "Bug Changes" in the selection "where one or more of the following changed:" fields "Alias" and "Whiteboard" are accessible. Reproducible: Always Steps to Reproduce: 1. Set parameters usestatuswhiteboard and usebugaliases to OFF values 2. Open query page. https://bugzilla.mozilla.org/query.cgi for example. Actual Results: In box "Bug Changes" in the selection "where one or more of the following changed:" fields "Alias" and "Whiteboard" fields will be accessible. Expected Results: If I switch off whiteboard and bugaliases fields in configuration then I shouldn't see these fields in the query page.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: PC → All
Summary: In query page fields which are switched off in configuration are accessible → Fields that are switched off are still listed in boolean charts on query.cgi
Target Milestone: --- → Bugzilla 3.2
Version: unspecified → 3.0.4
Bugzilla 3.2 is restricted to security bugs only. Moreover, this bug is either assigned to nobody or got no traction for several months now. Rather than retargetting it at each new release, I'm clearing the target milestone and the bug will be retargetted to some sensible release when someone starts fixing this bug for real (Bugzilla 3.8 more likely).
Target Milestone: Bugzilla 3.2 → ---
I agree. I just saw this problem on an installation which doesn't use the target milestone at all, and being able to query on it is really confusing.
This seems to be a duplicate of Bug#443306
Not a duplicate. This bug is about the "Search By Change History" section, not boolean charts.
Summary: Fields that are switched off are still listed in boolean charts on query.cgi → Fields that are switched off are still listed in the "Search By Change History" section in the Advanced Search page
You need to log in before you can comment on or make changes to this bug.