From f4966aeb0e7a655c986aeb285c1a220274ddbfd9 Mon Sep 17 00:00:00 2001 From: "lpsolit%gmail.com" <> Date: Mon, 22 Aug 2005 01:16:40 +0000 Subject: Bug 70907: QuickSearch: port the JS code to perl (make it server-side) - Patch by Marc Schumann r=wicked a=myk --- quicksearchhack.html | 357 --------------------------------------------------- 1 file changed, 357 deletions(-) delete mode 100644 quicksearchhack.html (limited to 'quicksearchhack.html') diff --git a/quicksearchhack.html b/quicksearchhack.html deleted file mode 100644 index d514082f8..000000000 --- a/quicksearchhack.html +++ /dev/null @@ -1,357 +0,0 @@ - - - - - Bugzilla QuickSearch (for Hackers) - - - - - - - -

Bugzilla QuickSearch (for Hackers)

- -

-Type in one or more words (or word fragments) to search for: -

- - - - - -

-This is a case-insensitive ``all words as substrings'' search; -words are separated by spaces. -By default, the following fields are relevant: Summary, Keywords, -Product, Component, Status Whiteboard. If a word looks like a part of a -URL, that field is included in the search, too. -

-The generic format for a ``word'' is - field1,...,fieldN:value1,...,valueM . -A bug qualifies if at least one of the values occurs as a substring in -at least one of the fields. -For example, assignee,reporter,qa:ibm,sun -will give you bugs where the assignee, reporter, or qa contact -has an email address that contains - ibm or sun . -If only value1,...,valueM is given, -the prefix (roughly) defaults to summary,keywords,product,component,statuswhiteboard: as noted above. -You can use -word to express the logical negation -of word. -

-Here is a complete listing of available fields (the Shortcut column is just -for access speed): -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Searched by default	Shortcut	Field Name	Aliases	Description
	`UNCO,NEW,...,CLOS, FIX,DUP,...(as first word)`	`status`		Status - ("bug_status") -
	`UNCO,NEW,...,CLOS, FIX,DUP,...(as first word)`	`resolution`		Resolution
	as-is	`platform`		Platform ("rep_platform")
		`os`	`opsys`	OS ("op_sys")
	`p1,p2` or `p1-2`	`priority`	`pri`	Priority
	`blo,cri,...,enh`	`severity`	`sev`	Severity ("bug_severity")
	@assignee	`assignedto`	`assignee, owner`	Assignee ("assigned_to")
		`reporter`	`rep`	Reporter (email)
		`qa`	`qacontact`	QA Contact (email) ("qa_contact")
		`cc`		CC (email)
yes	:area	`product`	`prod`	Product (enum)
yes	:area	`component`	`comp`	Component
		`version`	`ver`	Version (enum)
		`milestone`	`target, targetmilestone`	Target Milestone ("target_milestone")
yes		`summary`	`shortdesc`	Bug Summary (short text)("short_desc")
		`description`	`desc, longdesc`	Bug Description / Comments (long text)
depends		`url`		URL ("bug_file_loc")
yes		`statuswhiteboard`	`sw, whiteboard`	Status Whiteboard ("status_whiteboard")
yes	!keyword	`keywords`	`kw`	Keywords
		`attachmentdesc`	`attachdesc`	Attachment Description ("attachments.description")
		`attachmentdata`	`attachdata`	Attachment Data ("attachments.thedata")
		`attachmentmimetype`	`attachmimetype`	Attachment mime-type ("attachments.mimetype")

- -

-Examples for some useful abbreviations: -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Syntax	Semantics and Examples
:area	product,component:area
sev	severity:sev
`blo,cri,maj`	severe bugs
`enh`	enhancement requests
plevel	priority:level
`p1`	very high-priority bugs
`p1-2`	high-priority bugs
@assignee	assignedto:assignee
!keyword	keywords:keyword

- -

-More information can be found in the -"Features" section -on the introductory page. -

- - - - -- cgit v1.2.3-24-g4f1b