Bug 171866
Summary: | Search in "report bug" broken (expects special keywords) | ||
---|---|---|---|
Product: | [Community] Bugzilla | Reporter: | Craig Ringer <craig> |
Component: | Bugzilla General | Assignee: | PnT DevOps Devs <hss-ied-bugs> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | David Lawrence <dkl> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 3.2 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://bugzilla.redhat.com/bugzilla/easy_enter_bug.cgi | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-11-07 16:14:22 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Craig Ringer
2005-10-27 09:14:26 UTC
I concur. It seems the backend is attempting to look in the keyword field within the database rather than in the summary. (or the summary text needs to be changed to keyword). Hence, when user enters non-legit keywords the search always fails. Pretty important to fix this as this is the way in generating a bug report, and if search fails to find bugs that should have been shown, there is likely to be duplicates entered. Looks like the page is not causing form submission generated by enter to go through: function SearchForBugs( words, searchRadio ) This has another side affect: if no search term is entered, then a search begun by the enter key, it takes a couple of minutes of 5 step standby.gif scrolling through, before I cancelled the web page load. Hopefully it's not doing bad things to the bz db server (dos-ish). 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. |