It would be nice if we could create maniphest queries which were parameterized by the viewer's PHID. For example, I might like to have a query which was "All tickets I'm CC'd on", and there seems to be no reason for me to have to hardcode my own name in that query. If instead I could use a variable like $USER, then I could share that query with other people without everybody having to edit it to put their own name in. Additionally, then the built-in "Authored" and "Assigned" saved queries could actually be implemented using the normal saved query stuff rather than being hardcoded in PHP. Double-win!
Revisions and Commits
- Mentioned In
- T10574: A pathway toward "All Reviewers Must Accept"
T6579: Display hovercards on Tokens in Typeaheads
T5403: Display more high-level info in project hovercards
T7909: Allow ascending order for Conduit's maniphest.query's "order" parameter (order-created, order-modified)
D12509: Implement a scope selector for the global search
T7858: Typeahead/Tokenizer Errata
T3670: Add subprojects
T7729: No Typeahead on Herald object rule creation
T7566: Implement "Rooms" in Conpherence
T7251: Feature Request: Product Studio style query builder and tabular report
T6943: Create "basic" and "advanced" modes in Maniphest Search UI
T7197: AND/OR/NOT dropdown for "projects" search selectors
D11306: Maniphest - allow for searching for tasks based on dependency relationships
T6860: Allow creation of parameterized application policies
T6639: Be able to search for tasks as assigned to members of a project/team
T5288: Add a filter to show projects that I haven't joined
T5746: Phabricator does not show project color in Projects Typeahead field
D10491: Projects - add a filter to show not joined projects
- Mentioned Here
- T7858: Typeahead/Tokenizer Errata
D12444: Implement viewer() and members(project) typeahead functions
T3670: Add subprojects
- Duplicates Merged Here
- T6313: Is there a "current user" that can be used in maniphest queries for dashboards
T5670: Can't assign tasks to "none" when username is taken
T5585: Maniphest query - Need triage of project that i am a menbers of / dashboard
T5287: support 'me' as a user
T5635: Add builtin query for tasks in projects I am part of, with status open
T5633: Add builtin query for tasks that are assigned to me, but have no blockers
In D12444 I changed the default Differential query to use viewer(), instead of implicitly resolving the user's PHID. That means that when you "Edit Query", you get:
Responsible Users: [ Current Viewer ]
...instead of this, which is what you'd see previously:
Responsible Users: [ epriestley ]
I'm leaning toward reverting this. While using viewer() helps users discover tokenizer functions, I think these are a pretty advanced feature, and a new user is more likely to get a more useful understanding by seeing their own name (i.e., it implies "I can type a username to chose a user", while the viewer() token doesn't really suggest anything helpful about the typeahead).
It also makes the "Edit Query -> Change Something -> Execute -> Share URL" workflow more confusing, because the URL with someone else as the viewer will show them a completely different result set. (And if the recipient is logged out, the query will fail with an error.) This probably isn't very common, but using "epriestley" gives this workflow more predictable behavior.
Defaulting to viewer() never seems better for workflow reasons (except in cases where whoever is editing the query is sophisticated and intentionally trying to construct a parametrized query, but we don't need to look out for sophisticated users as much), and I think it's advanced enough that it doesn't make sense to try to drive function discovery on a user's first encounter with typeaheads. Function results show up as normal typeahead results and are discoverable through "Browse..." and will get documented at some point. These feel more appropriate for discovery of this feature than surfacing defaults in terms of tokenizer functions.
A big chunk of this is in HEAD. This should be where we are, roughly:
- All typeaheads/tokenizers should still work correctly.
- "Browse" button should work correctly everywhere.
- Differential "Responsible Users" field should now let you you use viewer() and members() functions.
This stuff is still known to be janky:
- Design needs a bit of work.
- Every search UI should support functions.
- We should have more functions.
- Function sort order can probably be better.
- Browse UI could probably do a better job of explaining function tokens.
- Browse UI dialog title is off.