Page MenuHomePhabricator

New saved custom search implicitly affects global search
Closed, ResolvedPublic

Description

A neat trick is that the top search here https://secure.phabricator.com/search/query/edit/ influences the native global search. This is cool if you really only want to search tasks...unless you specifically say. But it's not clear that the relationship exists and since a new saved search is placed at the top there users keep messing up their global search by saving a custom search for a particular thing.

(When they influence their global search by say limiting it to a project or something it is really confusing and was aptly described yesterday as "black magic")

Could we:

  • Make a new saved search insert at the bottom of the list so it doesn't hijack global search by default?
  • Put some text or indication on /search/query/edit/ that the top search will change how global search works?

There would be much rejoicing.

Event Timeline

chasemp raised the priority of this task from to Needs Triage.
chasemp updated the task description. (Show Details)
chasemp added a project: Search.
chasemp added a subscriber: chasemp.
scfc added a subscriber: scfc.Feb 13 2015, 5:37 PM
chasemp updated the task description. (Show Details)Feb 13 2015, 5:44 PM
qgil added a subscriber: qgil.Feb 13 2015, 5:56 PM
qgil added a comment.Feb 13 2015, 10:10 PM

I think that what actually confuses users is that the default option for general search after they register is not "Open tasks". Whenever they use the search field in the header, they get all those commits mixed with tasks, and they wonder why.

The fact that the customization of the default search is not easy to discover is a problem indeed, but the original problem is that Phabricator's default option seems to confuse many users (in our instance, at least). Admins have no way to change the default for all users.

Just curious, what is your default option for the general task? I have "Open Tasks", also here.

joshuaspence renamed this task from New saved custom search implicitly affects global search (confusing at least our users :) to New saved custom search implicitly affects global search.Feb 14 2015, 9:38 AM
In T7266#96398, @qgil wrote:

I think that what actually confuses users is that the default option for general search after they register is not "Open tasks". Whenever they use the search field in the header, they get all those commits mixed with tasks, and they wonder why.

I have created a task specifically about this problem at T7314: Default Phabricator search criteria confuses new users mixing commits and tasks

I've marked D12509 as fixing this, although it really just obsoletes it. Specifically: it removes this behavior (we no longer default to the first query) and makes scope selection explicit instead (if you want to default to a specific query, just select it from the dropdown).