I agree we need a more user friendly way of resolving IDs. (And, in passing, I think we also need an API method /resolve for programmatically resolving PIDs.)
But rather than adding a separate search form, I think we should generalize the current one, to be a Google-style, catch-all search box.

In the beginning, it could be something as simple as: "if it looks like a PID, then resolve it; else, do origin search". In the future it can be extended to other syntactical searches, such as file name search, commit ID search, etc.

The UI would be much better that way, and it'll always be possible to have a separate "advanced search" page (and/or special search keywords, like search engines do) where the various kinds of searches are broken down by type.

In T1118#20738, @zack wrote:

...
In the beginning, it could be something as simple as: "if it looks like a PID, then resolve it; else, do origin search". In the future it can be extended to other syntactical searches, such as file name search, commit ID search, etc.

The UI would be much better that way, and it'll always be possible to have a separate "advanced search" page (and/or special search keywords, like search engines do) where the various kinds of searches are broken down by type.

I completely agree