Bug 88130 – searching multiple versions of "bugzilla" fails to find anything

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 88130 - searching multiple versions of "bugzilla" fails to find anything

Summary:	searching multiple versions of "bugzilla" fails to find anything

Status:	CLOSED CURRENTRELEASE

Aliases:	None

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

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

URL:	https://bugzilla.redhat.com/bugzilla/...
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2003-04-06 09:26 EDT by Michael Schwendt
Modified:	2007-04-18 12:52 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2003-04-08 11:15:06 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.)

Groups: None (edit)

Description Michael Schwendt 2003-04-06 09:26:24 EDT

Simple search for reports in _multiple_ versions of "bugzilla" fails to find any
reports. 

Version-Release number of selected component (if applicable):
2.17.1

How reproducible:
always

Steps to Reproduce:
1. Simple search, Product "bugzilla", Component "bugzilla", Version "2.8 and
2.17", don't touch any other default settings.
2. Start "Search".
 
Actual results:
Zarro Boogs found.
(See URL).

Expected results:
Should find many bugs, all those that are found upon searching version "2.8" (or
"2.17") separately.

Comment 1 David Lawrence 2003-04-08 11:15:06 EDT

Should be fixed now do to a recent change i reverted. Please reopen this report
if this problem is still occuring.

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