Comment #23 on issue 7468 by krtulmay: Regression: Lost focus  
on "History", "Downloads" pages and "Find-in" box
http://code.google.com/p/chromium/issues/detail?id=7468

But the flip-side of that argument is that no matter what the default  
search for
issues is doesn't mean all that much, especially for a bug-tracking  
application, and
especially for users who get to the point of going to the bug-tracker and  
wanting to
submit a bug.

Users of a bug-tracking application should have the cognizance that any  
potential
problem they wish to submit may have already been identified by someone  
else and may
also already be fixed.  Their first step should ideally be to search for  
potential
existing issues to avoid unnecessary duplicates and review already reported  
details
that may aid/relate to their issue.

For this bug specifically, the current Verified state is definitely the  
correct
status.  What else could it be?  It's definitely not any of the  
investigative states
because the resolution is known and already implemented, and also been  
verified by
QA.  You don't question the status of the bug just because people are not  
searching
for it properly.

The onus of using a bug-tracking application successfully is on the users  
to think
carefully and search effectively.  Of course, it may help if the default  
issue search
was for All Issues, but then you will have the other side complaining that  
they only
care about open stuff left to be resolved.  (Perhaps default open is better  
for
developers?)  Regardless, bug-tracker users need to comprehend the need for  
searching
closed issues and any other search parameters to use a bug-tracker well.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---

Reply via email to