For what is worth, I believe the main use case for this are Maniphest tasks: someone complaining about X in social media or tools like Discourse, then someone replies pointing to a related Phabricator task.

@epriestley thank you very much for looking into this so quickly and in such detail. I fully understand that it is not worth investing a lot on this task. I thought this would be almost an easyfix, and I have learned something understanding the complexities (and the fact that OneBox hardcodes quite a bit of the fancy boxes).

I mean in the web notifications.

You can test with "Discovery" at https://phabricator.wikimedia.org/

In T5267#176885, @epriestley wrote:

• We get a "sync" process working, so strings can be imported from Phabricator to Translatewiki.
• We get an "export" process working, so strings can be exported from Translatewiki to a format we can read.

This is an invalid task here, but in any case https://phabricator.wikimedia.org/ does work, also for anonymous users.

Is this task open to be Prioritized? Wikimedia is discussing the possibility to fund it at https://phabricator.wikimedia.org/T135327

Is this task open to be Prioritized? Wikimedia is discussing the possibility to fund it at https://phabricator.wikimedia.org/T135327

Thank you for the explanation, @chad, very useful.

I'm happy with the new UI but only because I happen to work with a monitor in portrait mode. :)

Thank you for the quick fix! As for the fate of the misplaced tasks, don't worry, I'll deal with them.

For your information, we have closed the original report of this task at https://phabricator.wikimedia.org/T75715 as Declined.

Let me add that this is a problem that can be related and subjective, depending of the quality of your monitor and your vision.

See also T4788: Allow "Edit Dependencies" both ways (blocking and depending)

In T8376#120613, @epriestley wrote:

In Wikimedia it occasionally happens that we do things in private ... but usually the fact that we're working on something in private isn't private in itself

What I didn't explain is that this Phabricator header was one of the most contentious topics among some of our most experienced volunteers and some of my managers too. They were happy to fork the header and assume the cost of maintaining the local code. I calmed the discussion by promising that one day this will be fixed. So yes, communities care about their logos.

We call it "Wikimedia Phabricator" and our community talks about "Phabricator". Therefore [Wikimedia logo] + "Phabricator" makes sense, while "[What is this spooky eye?] + "Wikimedia" will create more confusion than the vanilla Phabricator header. I think the perceptions in other communities using Phabricator will be similar. All of them know their own logos, and all of them will recognize "Phabricator".

Related: Phabricator need structured way of relating non-blocking tasks to each other (like Bugzilla's "See also"), showing that relation in both tasks
https://phabricator.wikimedia.org/T76101

Tangential, and feel free to ignore if here and now it's not appropriate: in the lines of T6787: Clarify UI for Objects with a non-default Policy, I think it would be useful to have a clear visual cue signaling that you are in a non-public space.

(@Krenair, yes, the intention is that Spaces will allow us to deprecate our own local remedies, one step at a time.)

In T8493#119786, @epriestley wrote:

I created a test task (T8497) which only I can see, then I replied to it via email.

The workflow you showed is perfect, thank you. At least in Wikimedia nobody has asked for separate queues and I don't think anybody needs them.

Since "Assigned" is a search query, I'll ask here just in case: