I'd like to share result of quick investigation I made on how other issue trackers implement the similar functionality: - Jira - by default search globally with possibility of later project selection - YouTrack - project selector for search is part of top navigation. "All projects" option is selected by default but user can change project before searching - Redmine - search within project by default with possibility to select "All projects" later
As you see, there is no common approach here :) We can introduce a setting whether the default search should be performed within product scope or globally and tune this later based on feedback from users. Cheers, Andrej On 22 March 2013 12:12, Joachim Dreimann <[email protected]> wrote: > On 22 March 2013 04:10, Olemis Lang <[email protected]> wrote: > >> On 3/21/13, Joachim Dreimann <[email protected]> wrote: >> [...] >> > >> > To be clear: I have no objection in principle to us having a local search >> > box like this on our product pages, my objection is against changing the >> > scope of the search box in the header. >> > >> >> I think I follow you now . If that's the case I'd suggest to change >> search box placeholder with «Search all products. Try #EF-492» i.e. >> 'anything' => 'all products' . >> >> [...] >> >> -- >> Regards, >> >> Olemis. >> > > I've committed this as: > «Search all products. Try TracLinks» in r1459710. > > #EF-492 was just an example I used in an early HTML mockup. The intention > then is not really worth going into now; searching for TracLinks will be > much more helpful to users than a 'No matches found.' error page. > > Cheers, > Joe > > -- > Joe Dreimann | *User Experience Designer* | WANdisco<http://www.wandisco.com/> > > @jdreimann <https://twitter.com/jdreimann>
