Bug 202051 - empty summary/comment field with simple/advanced query doesn't work
Summary: empty summary/comment field with simple/advanced query doesn't work
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General (Show other bugs)
(Show other bugs)
Version: 2.18
Hardware: All All
medium vote
Target Milestone: ---
Assignee: David Lawrence
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2006-08-10 15:46 UTC by Nils Philippsen
Modified: 2007-04-18 17:47 UTC (History)
1 user (show)

Fixed In Version: 2.18
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-09-07 16:25:13 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Nils Philippsen 2006-08-10 15:46:16 UTC
Description of problem:

Without specifying one of the "Summary" or "Comments" search fields, both simple
and advanced query end up in:

Relevance Without Full Text Search
You can't see or sort by the 'relevance' field if you aren't also doing a full
text search.

Please press Back and try again.

If I add "&order=bugs.bug_id" to the URL, it works fine again, i.e. it tries to
sort per relevance which it can't do if both fields are empty, so perhaps it
should just assume "order=bugs.bug_id" if that is the case.

Comment 1 David Lawrence 2006-08-10 17:28:01 UTC
Can you paste the contents of your LASTORDER cookie?

Comment 2 Nils Philippsen 2006-08-11 08:11:30 UTC
It's "relevance".

Comment 3 Alex Lancaster 2006-09-07 12:17:03 UTC
I have the same problem, also reported on bug #202051.  Please fix soon, it
makes bugzilla.redhat.com unusable.

Comment 4 David Lawrence 2006-09-07 16:25:13 UTC
Removed reference to relevance and chose standard order of bug_id. Please clear
out any bugzilla.redhat.com LASTORDER cookies using your browser preferences and
try your searches again. Please reopen bug if doesnt solve for you.

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