Bug 82741 – can't set default query without running it

Bug 82741 - can't set default query without running it

Summary:	can't set default query without running it

Status:	CLOSED UPSTREAM

Aliases:	None

Product:	Bugzilla
Classification:	Community
Component:	Bugzilla General (Show other bugs)
Sub Component:
Version:	3.2
Hardware:	All Linux

Priority	medium Severity low (vote)
Target Milestone:	---
Target Release:	---
Assigned To:	PnT DevOps Devs
QA Contact:	David Lawrence
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2003-01-25 11:38 EST by Jay Berkenbilt
Modified:	2013-06-23 23:08 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2008-09-16 13:35:42 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Mozilla Foundation	455545	None	None	None	Never

Groups: None (edit)

Description Jay Berkenbilt 2003-01-25 11:38:19 EST

Description of problem:

In the old (2.8-based) bugzilla interface, it was possible to set a deafult
query without running the query.  Now it seems that setting something as a
default query has to be done in conjunction with executing the query.  This is
somewhat undesirable in some cases.  My default query is always set to search
the current beta, rawhide, and the most recent release.  I always have no
components selected.  Executing that query would return a huge number of bugs. 
I never actually make my default query; I just use it as a convenient starting
point.

Luckily, it works to execute the query and stop it before it returns any resuls....

Comment 1 David Lawrence 2006-04-08 13:49:49 EDT

Red Hat's current Bugzilla version is 2.18. I am moving all older open bugs to
this version. Any bugs against the older versions will need to be verified that
they are still bugs. This will help me also to sort them better.

Comment 2 Jay Berkenbilt 2006-04-08 13:55:00 EDT

I can confirm that this "bug" is still present in Red Hat's current Bugzilla.  I
can't swear to it, but I believe this problem is present in bugzilla's current
upstream as well.

Comment 3 Jay Berkenbilt 2007-11-26 12:49:55 EST

It's amusing that this bug is still "new" after almost five years.

Comment 4 David Lawrence 2008-09-16 12:49:47 EDT

Red Hat Bugzilla is now using version 3.2 of the Bugzilla codebase and therefore this bug will need to be re-verified against the new release. With the updated code this bug may no longer be relevant or may have been fixed in the new code.
Updating bug version to 3.2.

Comment 5 Jay Berkenbilt 2008-09-16 13:19:13 EDT

I can confirm that this behavior is still present in 3.2.  Maybe I should just report this to mozilla's bugzilla, which is probably what I should have done over 5 years ago....

Comment 6 David Lawrence 2008-09-16 13:24:34 EDT

We are running very close to stock upstream code so if you do not mind, please file this in the upstream Bugzilla and then the fix will trickle down to us.
Once you have done that post the new bug link here and close as UPSTREAM resolution.

Thanks
Dave

Comment 7 Jay Berkenbilt 2008-09-16 13:32:33 EDT

Crossed in the mail.  Here's the upstream report I just entered:

https://bugzilla.mozilla.org/show_bug.cgi?id=455545

Comment 8 Jay Berkenbilt 2008-09-16 13:35:42 EDT

closed "upstream" as per request.  Thanks.

Note You need to log in before you can comment on or make changes to this bug.