Closed Bug 275019 Opened 20 years ago Closed 20 years ago

query defaults are selected in query.cgi when only boolean chart params are passed

Categories

(Bugzilla :: Query/Bug List, defect)

2.17.6
defect
Not set
normal

Tracking

()

RESOLVED FIXED
Bugzilla 2.16

People

(Reporter: timeless, Assigned: jacob)

References

()

Details

Attachments

(1 file, 1 obsolete file)

expected results: because params are provided to query.cgi, only the params to query.cgi are used to fill the form actual results: resolution=---|duplicate is also selected
timeless: are you sure this is a regression? Gerv
This is not a regression, I can reproduce this on 2.16.7 It appears to only happen with the boolean chart fields. If the only params you pass in are boolean chart related, it fills the default query AND your params.
No longer blocks: bmo-regressions-0412
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: blocking2.20+
Flags: blocking2.18+
Flags: blocking2.16.8+
Target Milestone: --- → Bugzilla 2.16
Whiteboard: bug awaiting patch
Attached patch Patch v1 (obsolete) — Splinter Review
This patch should work for the tip, 2.18 and 2.16.
Assignee: justdave → jake
Status: NEW → ASSIGNED
Attachment #169280 - Flags: review?
Whiteboard: bug awaiting patch → patch awaiting review
Arr. OK, the summary was really confusing, changing slightly. (It took me a few minutes to understand what the bug was about, when I wanted to review it.)
Summary: default resolution query is selected even when query is passed some params → defaults for "resolution" are selected in query.cgi even when query.cgi is passed some params
Comment on attachment 169280 [details] [diff] [review] Patch v1 >+ # If the name begins with field, type, or value, then it is part of >+ # the boolean charts. Because these are built different than the rest >+ # of the form, we don't need to save a default value. We do, however, >+ # need to indicate that we found something so the default query isn't >+ # added in if all we have are boolean chart items. >+ if ($name =~ m/^(?:field|type|value)/) { >+ $foundone = 1; >+ } This looks great. I tested it on the tip, 2.18-branch, and 2.16-branch, and it works fine. >@@ -395,6 +403,9 @@ > $vars->{'category'} = Bugzilla::Chart::getVisibleSeries(); > } > >+$vars->{'known_name'} = $cgi->param('known_name'); >+ >+ > # Add in the defaults. > $vars->{'default'} = \%default; This looks like it's part of a separate patch, as there is no known_name var needed in the 2.18 templates, and this patch is already checked-in on the tip. Make SURE to remove this section before checkin.
Attachment #169280 - Flags: review? → review+
Flags: approval?
Flags: approval2.18?
Flags: approval2.16?
Whiteboard: patch awaiting review → patch awaiting approval
(In reply to comment #5) > >@@ -395,6 +403,9 @@ > > $vars->{'category'} = Bugzilla::Chart::getVisibleSeries(); > > } > > > >+$vars->{'known_name'} = $cgi->param('known_name'); > >+ > >+ > > # Add in the defaults. > > $vars->{'default'} = \%default; > > This looks like it's part of a separate patch, as there is no known_name var > needed in the 2.18 templates, and this patch is already checked-in on the tip. > Make SURE to remove this section before checkin. Yep, it is. I think it's from a patch that already landed... but I don't remember for certain :)... definately need to make sure it's not in the patch that gets checked in.
Hardware: Macintosh → All
I think a new patch with the unnecessary lines removed would be a good idea...
(In reply to comment #7) > I think a new patch with the unnecessary lines removed would be a good idea... I agree. I want one here before I approve it for checkin. Especially since this is something people who pick and choose patches to apply to old installs might be likely to grab.
Attached patch Fixed PatchSplinter Review
OK, here's the same patch with that section removed.
Attachment #169280 - Attachment is obsolete: true
Attachment #169949 - Flags: review+
Flags: approval?
Flags: approval2.18?
Flags: approval2.18+
Flags: approval2.16?
Flags: approval2.16+
Flags: approval+
Summary: defaults for "resolution" are selected in query.cgi even when query.cgi is passed some params → quert defaults for "resolution" are selected in query.cgi even when query.cgi is passed some params
Summary: quert defaults for "resolution" are selected in query.cgi even when query.cgi is passed some params → query defaults are selected in query.cgi when only boolean chart params are passed
Checked into tip, 2.18, and 2.16. Checking in query.cgi; /cvsroot/mozilla/webtools/bugzilla/query.cgi,v <-- query.cgi new revision: 1.134; previous revision: 1.133 done Checking in query.cgi; /cvsroot/mozilla/webtools/bugzilla/query.cgi,v <-- query.cgi new revision: 1.126.2.3; previous revision: 1.126.2.2 done Checking in query.cgi; /cvsroot/mozilla/webtools/bugzilla/query.cgi,v <-- query.cgi new revision: 1.98.2.3; previous revision: 1.98.2.2 done
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Whiteboard: patch awaiting approval
*** Bug 203951 has been marked as a duplicate of this bug. ***
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: