Bugzilla – Full Text Bug Listing
| Summary: | Search for existing bugs does not search for closed bugs? | ||
|---|---|---|---|
| Product: | Community | Reporter: | dca <dcahh> |
| Component: | Bugzilla | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | remy.suen |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | stalebug | ||
|
Description
dca
If you go to the quick search page [1] you'll see that it only searches "open" bugs by default. Quick search seems to behave the same way. The results page does show that only the following status were searched: Status: REOPENED, NEW, ASSIGNED, UNCONFIRMED I guess quick search doesn't want to clutter up the display with results that may be irrelevant (closed bugs). I'll close this as WORKSFORME since this is by design. [1] https://bugs.eclipse.org/bugs/query.cgi?format=specific [ ] Clever ;o) Usually one does this: 1) Experiences a bug in Eclipse 2) Thinks "let's take a *second* to enter a bug..." 3) goes to Google: http://www.google.de/search?client=opera&rls=de&q=eclipse+bugs&sourceid=opera&ie=utf-8&oe=utf-8 4) Clicks the first seach result 5a) Thinks he is an anti-noob and does a quicksearch first... https://bugs.eclipse.org/bugs/buglist.cgi?quicksearch=titile OR 5b) he clicks "File a bug", chooses "Platform/Workbench" or whatever and is forced to do a quicksearch on that page https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Platform&format=guided 6) In any case he sees no bug and enters a new one. Result: double work for everyone. I don't think that's good design... maybe wanna change it? > I don't think that's good design... maybe wanna change it? Agreed. I've changed our template on the Simple Search screen to default to "All" instead of "Open". For the quicksearch, that required a simple code change. I don't want to do a custom hack for Eclipse.org since we like running vanilla software. I did track this down on Mozilla.org: https://bugzilla.mozilla.org/show_bug.cgi?id=319036 Coincidentally, doing a quick search for that on bugzilla.mozilla.org didn't show that bug :) This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. I'm going to close this as 'fixed' since a quick test shows that closed/resolved bugs are being returned on the quick search section of the guided bug entry. -M. |