Steps to reproduce:
In Logstash, investigating an output line, select the "Phatality" tab, and under "Phabricator actions" click the button.
Expected results:
Search results, ideally with additional context (project tags, date, etc), ideally without tickets marked as feature requests, provided by more performant Phabricator's Maniphest Advanced Search (class ManiphestTaskSearchEngine):
https://phabricator.wikimedia.org/maniphest/?statuses=open()&group=none&order=newest&query=%22Primary%22%20%22Global%22%20%22Advanced%22#R
Actual results:
Slightly error-prone search results without context, provided by less performant Phabricator's Primary Global Search (class ManiphestTaskFulltextEngine):
https://phabricator.wikimedia.org/search/?search:primary=true&search:scope=open-tasks&query=%22Primary%22%20%22Global%22%20%22Advanced%22#R
Other comments:
I'm unsure if there were particualr reason(s) behind using the primary (global) search with "open tasks" as a scope selector (CC'ing @Krinkle in case there's something I'm missing).
https://gerrit.wikimedia.org/r/plugins/gitiles/releng/phatality/+/96ea0062dd8c9d19cff1bed40b77d33fc9915a11 implies that the intention is to "search Phabricator for open tasks" anyway, so the set scope already excludes e.g. commits among global results anyway.
It seems already possible to use the dedicated "advanced" task search without code changes needed.
Disadvantage:
To get a short sharable URI with an alphanumeric identifier you need to run that query again.