Closed
Bug 344657
Opened 18 years ago
Closed 11 years ago
Should be able to search for the bug i'm filing
Categories
(Bugzilla :: Creating/Changing Bugs, enhancement)
Tracking
()
People
(Reporter: timeless, Unassigned)
References
()
Details
Currently I'm staring at Enter Bug: Bugzilla I was about to file a bug in Component: Whining. but I realized that I'm going to enter all the information I care about right now, esp picking a component (whining) and enter some words in description. Actual Results: Buttons: [ Commit ] [ Remember values as bookmarkable template ] Expected Results: [ Commit ] [ Search for a bug like this ] [ Remember values as bookmarkable template ] clicking that Search button should use all the fields I've selected to try to find the bug I'm about to file. Especially, if I fill in a component, then the query should convert that component into a boolean chart: {Components is <x>} OR {Comment contains <x>} Version, Platform, OS, Severity, and State should be ignored. If the number of matches is greater than 10, then they should be used to refilter the results by number in this order (switching from filtering to sort favoring when the number drops below 10): Some magic is required here: {bug number is <bugnumberlist>} AND {Summary MAGICMATCHES <summary>} if the list is > 10, then let bugnumberlist=resultlist if the list is 0, then drop the criteria if the list is <10, then order those numbers that match before ones that don't and retain two lists. {bug number is <bugnumberlist>} AND {Summary MAGICMATCHES <comment>} if the list is > 10, then let bugnumberlist=resultlist if the list is 0, then drop the criteria if the list is <10, then order those numbers that match before ones that don't and retain two lists. {bug number is <bugnumberlist>} AND {Comment MAGICMATCHES <summary>} if the list is > 10, then let bugnumberlist=resultlist if the list is 0, then drop the criteria if the list is <10, then order those numbers that match before ones that don't and retain two lists. {bug number is <bugnumberlist>} AND {Comment MAGICMATCHES <x>} if the list is > 10, then let bugnumberlist=resultlist if the list is 0, then drop the criteria if the list is <10, then order those numbers that match before ones that don't operating on your two preexisting lists. bugs 1 2 3 4 5 6 7 8 9 10 11 are ordered: 4 existing-Summary MAGICMATCHED proposed-Summary and existing-Comment MAGICMATCHED proposed-Summary and existing-Summary MAGICMATCHED proposed-Comment and existing-Comment MAGICMATCHED proposed-Comment 5 existing-Summary MAGICMATCHED proposed-Summary and existing-Comment MAGICMATCHED proposed-Summary and existing-Summary MAGICMATCHED proposed-Comment 6 existing-Summary MAGICMATCHED proposed-Summary and existing-Comment MAGICMATCHED proposed-Summary and existing-Comment MAGICMATCHED proposed-Comment 7 existing-Summary MAGICMATCHED proposed-Summary and existing-Comment MAGICMATCHED proposed-Summary and existing-Comment MAGICMATCHED proposed-Comment 8 existing-Summary MAGICMATCHED proposed-Summary and existing-Summary MAGICMATCHED proposed-Comment and existing-Comment MAGICMATCHED proposed-Comment 9 existing-Summary MAGICMATCHED proposed-Summary and existing-Comment MAGICMATCHED proposed-Summary 10 existing-Summary MAGICMATCHED proposed-Summary and existing-Comment MAGICMATCHED proposed-Summary ... something like that. Yes, we're micro sorting, and yes the algorithm for this can be split into another bug if necessary, but it'd be good. I'm not sure how to define MAGICMATCH. words like "be", "I", "the" and "should" should drop out from match searching except when part of quotations. each quotation should be used in its entirety or dropped. I'm not sure how to deal w/ it, magicmatch could be taught a list of stopwords or something. {bug number is <bugnumberlist>} AND {Platform is <x>} If the number drops to zero then a field should be ignored, so if platform=PC drops my results to zero, continue to the next field: {bug number is <bugnumberlist>} AND {OS is <x>} when the list reaches a number less than 10, the remaining criteria should be used to affect sorting. {bug number is <bugnumberlist-from-platform-os} AND {Severity is <x>} If that gives fewer hits then those hits should be ordered before: {bug number is <bugnumberlist-from-platform-os} AND {Severity is not <x>}
Comment 1•17 years ago
|
||
Confirming that it could be good to have a "Search for similar bugs" button, but not with the logic suggested by timeless. The button should open a new tab/window to not loose data already entered in the form.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: PC → All
Comment 3•11 years ago
|
||
Automatic duplicates detection has been implemented in Bugzilla 4.0.
Status: NEW → RESOLVED
Closed: 11 years ago
Keywords: helpwanted,
ue,
uiwanted
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•