I'm going to close this in favor of T13602, which has a more cohesive/modern discussion of the issue. Broadly:

Spaces have been working great for my install. The only real place where they're lacking I think arises from their coarseness/mutual-exclusivity.

I think (?) this was pretty much resolved by the last round of changes. See T13291 for some followups.

See T13357 for followup.

There's currently a bug (likely related to D20652 or D20654?) where normal edits aren't respecting card order correctly during the redraw. I suspect this is just an order parameter getting lost somewhere.

a logical clock to complement the wall-time clocks

From D20653:

Just thinking out loud:

Here's roughly where I'm headed next. I'm planning to:

The "default" controller currently needs to "force" the URI parameters...
The "filter" controller currently needs to "force" the URI parameters...
The "apply" flow, where a new custom filter is applied...

A couple of weird cases on state management:

See also T13317.

PHI1224 describes a somewhat-adjacent situation: an install would like a way for external automated tooling to reference source files and generate editor links for them.

This is approximately coming into existence and this task no longer serves much of a purpose. See T13083 / T13279 for followups.

This now approximately exists and is no longer of much use as a standalone task. See T13279 and elsewhere for followups.

I believe this was resolved by D20327 / D20393.

To summarize the state of the world here:

I'm going to merge this into T12738. Although that task primarily discusses Nuance as a Phacility support tool and we ended up building a standalone Support tool instead, I generally believe Nuance is the most likely pathway for interactions falling under the general "helpdesk" umbrella.

This isn't an actionable task. It covers too much ground, describes too many features, and most of it lacks compelling use cases.

No plan to continue on this?

This is intended and has legitimate use cases.

In T8510#200946, @aklapper wrote:

In https://phabricator.wikimedia.org/T76732#2803813 ksmith brings up that "In the search bar in the toolbar at the top of the screen, searching for "Maps" brings up Maps as the third option. Searching for "Discovery" brings up Discovery as the second option."

After D19384, we'll automatically mark these "phantom" notifications as read when you open the menu to review them:

This will ultimately be covered by T13105.

See followup in T13105.

Also relevant:

(For completeness, this came up via the support queue in PHI411.)

This task is a giant mess with pretty much no remaining actionable use cases. See T13074 for plans. If you want some use case here included in that, file a description of your problem via support pact.

I second this:

Not all applications have full policy support yet, usually because it's blocked by something or they're beta.

In T5698#223992, @chad wrote:

Oh hai Cura uses Phabricator? I have a Lulzbot at home!

Oh hai Cura uses Phabricator? I have a Lulzbot at home!

@Krinkle, @pablocarrillo I second your requests. Great suggestion. I have a large README.md that I would love to split into multiple documentation files, without losing all the formatting.

This is also extremely silly, but I sometimes do it because I'm dumb and have muscle-memory for ⌘+1+⇥+⌘+V+⏎: searching for an object URL doesn't jump you to that object URL, but you probably meant to put it in the other box.