This is technically very easy but I'm still not really sold on the value.

D8685 provides some relief here, but I don't think that applies to Maniphest per say. In general we'll always be improving general UI libraries on Phabricator and Maniphest will get them for free. I don't see anything uniquely actionable here.

For now it's a 40x40px logo that will be replaceable. We'll have more options down the road once we redesign the header around Spaces and Flags.

Yes, I know, I was asking for a design-only mockup to show the direction you want to go. No problem, we will wait patiently for this one.

This isn't actually available yet, @chad just did the internal design bit. There will be a proper UI for it once I get around to writing it.

Is there a mock somewhere showing desired/recommended use(s) of an additional logo in the header?

Passing the torch.

We intend the header to be consistent across all Phabricator applications. While an open installation of Maniphest likely benefits from a more dramatic treatment, it doesn't make sense everywhere to me.

Only this would be extremely helpful, thank you.

We could also do something like:

(This task discuses some larger considerations; for now, do only the transaction colors, since the rest of this is muddy and amorphous.)

Some additional discussion in T6393#80853. In general:

Closed by commit rP97f05d6ab892.

@anne I'm not sure how you meant it, but your comment comes across as sort of weirdly passive-aggressive. By all means, if Maniphest isn't working for you, we encourage you to look at other options.

You may want to talk to @zeeg at Dropbox regarding Phabricator.

Not having a hierarchical view of tasks belonging to parent tasks is really getting in the way. And I think everyone expects a hierarchical task organization, so ditching multiple parents would be a much better compromise for us to get what we need here. In the absence of that, I'm going to try to get us to something taht works better. I'm relatively new to Dropbox and have used lots of other task management tools in the past that work much better in this way. So I am going to try to move everyone to something else. I wish that Maniphest did this for us.

Closed by commit rP800e3812bc58.

Closed by commit rPf5235f7e09eb.

The intention is to click the to pull up the other page.

Closed by commit rPORG73f7c4030a9a.

Nope, Yup: this is what I mean

This is on my short term radar

Just for your information, at https://phabricator.wikimedia.org/T707 we are discussing the best way to combine the Wikimedia and Phabricator logos in the header, considering the trademark and technical limitations. We want to do the right thing, if possible featuring the Wikimedia logo to assure our users that they are at home.

I've seen the ALLCAPS email like twice before, never been able to build a repo case. :(

Closed by commit rP58b75b15fa3c.

@chad not sure if that matters but @erdoan change triggered a mail notification in all upper case.

Closed by commit rP88efd8a3efb2.

Closed by commit rPd9ad4ab385c2.

Yes, it's a known issue.

Seeing the same thing on this instance:

Closed by commit rPf10fbb8600ea.

(and I will add pink then) ?

I'm going to triage this to fixing indigo anyways.

secret commits

Those seem reasonable to me, yeah.

@epriestley, what do you see worth putting on "Roadmap". SaaS? Harbormaster? Spaces?

Closed by commit rPed0b23cb4d41.

Oh, I didn't mean to imply this was important at all; just going through my notifications this morning. =D

I expect Namespaces will resolve most issues that installs run into and run multiple Phabricators to solve, since they'll just move to one instance. Beyond that it's not clear there is an actual problem, would rather wait until it surfaces and is apparent. Then we'd likely just build it into the bookmarking app or have an account dropdown. Either way, I'd want to solve it not just for Phacility but for large corp installs that still need multiple copies running as well.

Most of the support I am seeing here is about distinguishing between Phabricator instances. This support issue becomes more complicated if / when namespaces (T3820) lands - theoretically, now there are distinct instances and namespaces to be aware of at a glance.

agree - I am confused between our own install and the main phabricator and need to check URL often...

(Not related in the SAAS sense, although maybe we should split the tag up.)