Projects are searched for by the search bar, and groups are searched by filtering the list. Languages cannot be searched at all. The projects search bar could be repurposed to search for the important zanata features - groups, projects, languages - perhaps even documents! I believe we could be doing search better.
A few questions about scope and expected behaviour. I generally agree that we should have a unify search for project, groups, even documents and users, however: 1. What's the use case for language search? (Who actually need it?) Language are relatively static, i.e., it does not change much. Just a browser search is normally sufficient. For translators and language coordinator, they are more likely to join the languages they interested at the beginning, and then stick with that. Indeed occasionally they might join a few more, but then again, the browser search on language page is sufficient. For maintainers, they are more likely care about the statistics of ALL languages they want in, they don't need to search individual language. 2. What's the landing page should we provide language search? Currently our language related page is the user list of the specified language team. However, IMHO, if I were a translator join the language team, I am more interested in projects yet to be translated in my languages instead of seeing language team member. 3. Should we support incremental or substring search? 4. Should we allow the user to specify the parameters that they only want to search projects, groups and languages?
1. Language search may provide: - search [x] language, show projects that support that language - search [x] language, show language variants for that string 2. The landing page will either be that language, or the project supporting that language 3. I'm not really interested in that 4. No, it should be smart enough to work that out for itself Assigning to RFE owner.
Reassigned to PM
Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-176