When going through the process of entering a new bug, the search box in step one only brings up open bugs. This is essentially useless for a class of error which might be categorized as 'user error'. It would be useful to flag representitive bugs as they are closed so that they are included as appropriate in the step 1 search box. This way, people at least have a chance to realize they might have done something wrong. Reproducible: Always Steps to Reproduce: 1.Open NEW bug form 2. key in search terms 'emerge world' 3. view resulting list of currently open bugs. 4. open and look at bug 15944. I've seen this 'bug' come up before so it's a fairly common oversight even among people who actually know better (including me). I'm sure mhozler is probably tired of responding to these. ;-)
I would like to comment on another aspect to this bug. In the mentioned step 1, the user is encouraged to search for posted bugs as a way of avoiding dups. Here is a scenario I happened upon this morning. An ebuild has a bug. user1 emerges the ebuild. user2 finds and reports the bug. Developer fixes bug, closes bug report, and releases new ebuild. user1 finds the bug, searches for it, finds it not and reports it. We now have a dup that could easily have been avoided. The downside of including fixed bugs is that we get alot of spam in the search results. I therefore propose a checkbox to include or exclude closed bugs.
query is workable with the added ALL statement, I changed the main page to give people pointers in the future.
