I have the same problem with dependency search results. We’re dealing with a sizeable project right now with a bunch of parent tasks that have practically identical sets of subtasks. Trying to assign dependencies between the subtasks of any one of the parent tasks is a nightmare, because searching a subtask name brings up exactly the kind of situation seen in Randy’s screenshot.
The limit of 10 search results makes it physically impossible to set some dependencies, because the desired subtask simply doesn’t appear in the results list. I’m not sure what the sort order is for these results, but it’s clearly not by “proximity.” Most times I’m trying to select a sibling subtask within the same parent. You’d think such a sibling would show up first in the results, but it’s always somewhere random down the list, or it doesn’t make the 10-item cut at all.
Additionally, what makes this feature nearly unusable at times is when the subtask/task names are long enough to get cut off at the arbitrary width of the search results box. Sometimes I can’t accurately identify which result to choose, because I can’t see the full parent task title in order to differentiate them.