I believe D20336 fixes the primary practical issue here, by adding a "View All Results" button to the bottom of query panels (including query panels inside tab panels), when there are more results:

👍🏼

I think most everything here is complete and will file individual follow up tasks if needed.

(And it's easier to build query panels.)

I'm fine with getting rid of the template, I think it's much less relevant now that home is no longer a single dashboard.

Wondering if we should get rid of "template dashboard".

Mine's fine here, too:

Only 5? I expected more.

I imagine Facts will have similar workflows. The easier we can make it, the less worried I am about re-using panels.

Yep, that's what I'm thinking too.

Yeah, and the sane version (add to dashboard, not to tab panel) is probably not too awful and won't really make fixing T8033 any harder.

I want it to work like like installing to home does basically, see query, click add, confirm, get take to arrange with the panel built and added.

Yeah maybe I should optimize that workflow first, seems higher leveredged. T5307

Getting rid of all "Select Existing Panel" flows also makes simplifying the "Run a query -> turn it into a panel -> put it on a dashboard" workflow a bit more of a mess, especially if we want to try to do "run a query -> turn it into a panel -> add it to a tab panel". But I think in the long term making the T8033 problem impossible and then trying to do our best with the "query -> panel -> dashboard" flow is the best bet.

frickin' tab panels make everything 10x harder.

As long as you're selecting existing panels in any interface, we're stuck with the problem in T8033. I think we can only fix that elegantly by removing all interfaces where you select panels, and replacing them with interfaces where you create panels.

Or maybe icons... everyone loves icons.

If I add "short name" as an optional Panel field, I could get rid of naming tabs. Then you just have to select a bunch of panels.

The change I imagined there was:

If we make the permission changes discussed elsewhere (T8033, I think?), this might just become something like a containerPHID which points at a Dashboard for panels created from dashboards, another Panel for panels embedded in panels, and null for standalone panels.

Oh I see above you mention using edges too.

I don't think there is much value here in having "appears on", since panels work on dashboards, other panels, or any remarkup, anywhere. Does anyone have a good reason to keep this function? I could create an edge for panel -> panel if we want to keep something like this. But I'm concerned if the point is to "prune" panels, then we'd need to maybe build out mentions as well.

Resolved enough, unclear any benefit to installing to Favorites and Projects needs additional work to make it truly useful.

Ahh that did the trick - thanks.

For now, "Edit Menu" on your home, click "Global" and add the Dashboard. "Default" is the topmost dashboard. You can disable "Home" then. This will be easier after D17492 lands.

How exactly is this currently possible? I am trying to change the default homepage for all users but not managing to do that. Have tried creating a Dashboard, but not sure how I can use that to 'replace' the homepage for everyone.