Page MenuHomePhabricator

Make the default ApplicationSearch query explicit, not just the first item in the list
ClosedPublic

Authored by epriestley on Aug 14 2017, 6:13 PM.
Tags
None
Referenced Files
F19083673: D18422.id.diff
Tue, Dec 2, 1:16 PM
F19073105: D18422.id44275.diff
Mon, Dec 1, 12:44 AM
F19071752: D18422.id44267.diff
Sun, Nov 30, 8:41 PM
F19071397: D18422.id44365.diff
Sun, Nov 30, 7:28 PM
F18901974: D18422.diff
Nov 7 2025, 11:22 PM
F18812263: D18422.id44275.diff
Oct 20 2025, 7:59 AM
F18773843: D18422.id.diff
Oct 9 2025, 1:09 PM
F18768422: D18422.id.diff
Oct 8 2025, 3:28 AM
Subscribers
None

Details

Summary

Ref T12956. Currently, when you visit /maniphest/ (or any other ApplicationSearch application) we execute the first query in the list by default.

In T12956, I plan to make changes so that personal queries are always first, then global/builtin queries. Without changing the "default query" rule, this will make it harder to have, for example, some custom queries in Differential but still run a global query like "Active" by default. To make this work, you'd have to save a personal copy of the "Active" query, then put it at the top.

This feels a bit cumbersome and this rule is kind of implicit and a little weird anyway. To make this work a little better as we make changes here, add an explicit pinning action, like the one we have in Project ProfileMenus.

You can now explicitly choose a query to make default.

Test Plan
  • Browsed without pinning anything, saw normal behavior.
  • Pinned queries, viewed /maniphest/, saw a non-initial query selected by default.
  • Pinned a query, deleted it, nothing exploded.

Screen Shot 2017-08-14 at 11.05.40 AM.png (1×1 px, 154 KB)

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable