+lots for removing the words "storage containers" - projects are very much not "storage".
A better metaphor is "labels" or "index" (like in a printed book? Is that something young people know about?).

I'd like to keep this boring:
Projects are hashtags are tags. You can use them for code bases, teams, or anything you need to group.

Probably, the "color change" should be handled as "expanded transaction" - whatever it means - so that it changes only after its related cause (status change to → archived) and not always as long as the current value is archived.

In T15448#9857, @avivey wrote:

In any case, it should be generic - on "search results page", although probably requires each SearchEngine to define the available fields in order to actually support this feature.

Currently, only Commits show anything like "description" (commit hovercard shows the commit message.

Just as clarification do you have any other Hovercard in mind that has a description?

In any case, it should be generic - on "search results page", although probably requires each SearchEngine to define the available fields in order to actually support this feature.

Yep that is my current workaround. Premising I pretty damn like the current export engine in Maniphest. It should not be that impossible to replicate to Projects as well.

You can already "export" to json from the conduit. Maybe "teach conduit search methods to produce csv" would be a better solution.
Alternatively, an external script to convert the resulting json to a csv.

So apparently this is not a problem in the unit test itself but just with T15375

By the way it happened again here :D