I agree with the principle of not hiding, then, but note that currently Phabricator is hiding the whole homepage when only one panel doesn't fit with the policy. Anyway, this is a minor problem once you are aware of this.

I'm updating the task description of T4103 and rolling this up into it. We'd prefer in general not to hide stuff around permissions (which is why action links for example are grey if inactionable) and feel T4103 will resolve your main issue.

I'm fine if we just simplify it to Header + Current Layout Options. It'd likely solve 90% of the outstanding needs. I don't feel three column layouts are particularly useful for us (that is, we have a task for a 3 column, but it doesn't seem to have much interest).

Didn't you have to hand out candy tonight?

I think this is all remotely reasonable layouts, exhaustively:

I guess maaaaaaaaaaybe this is sort-of reasonable:

I think we can accommodate this with 1 + 2 and 1 + 3 layouts?

Dashboards are this weird product where we want people viewing and copying, but not editing other people's or archiving them (since they belong to someone else). I'd like to take a pass at providing better options to viewing the \dashboards\ home in this task and maybe with T4984 as well. If both these tasks don't make home a better experience, we can discuss then how to let admins clean things up (people without command line access).

Just make an advanced search and set it as the default.

Thanks @chad !

Replacing Project Pages with a customizable Dashboard seems like it'd solve most of these cases, at least.

Generally speaking, Phriction isn't our Product Management app. Workboards are, and maybe Dashboards to some other extent. We'd rather improve these to cover use cases that fit maybe how your company works, rather than pursue edge case use in Remarkup or Phriction. We have a lot planned around Workboards, and it is one of products we really want to have cover a lot of cases. Please take a look at Workboards and see what already is planned, and if something you'd think would benefit many Phabricator users is missing, feel free to file.

@chad what about being able to add filters for tasks and the like in dashboards so you can put tasks for project x on the wiki page for the same project without having all of your other projects, etc, showing? Is there any chance that something like that will be implemented?

You can already build a custom query as a Dashboard and embed it in Remarkup. As far as providing additional 'views', we're not pursuing any at this time.

I actually came here to suggest practically the same thing. I like what @adinnaplus is saying, custom queries for dashboards / workboards would be absolutely amazing.

Closed by commit rP6410d8fd1689.

That describes a more general fix, but I'm not going to pursue it for now.

The Editor needs null internal/external apply implementations to handle mentions. This is a ~4-line fix.

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.

In T6364#80346, @chad wrote:

Are they still grouped, but not labeled?

I can confirm that grouping works, just the headers do not display. Maniphest still returns old custom headers and hasn't been modernized yet, so they are just hidden on dashboards.

Are they still grouped, but not labeled?

The group by works perfectly from the /manifests/ search page showing up the nice list of tasks as described above with my leet ascii arts.

Three columns might be nice on a wide screen, but please please keep in mind people using small windows. I usually browse with a 1000 x 800 px window so 2 columns is a maximum for me.

Does the query also not respect this on the general maniphest search page?

Closed by commit rPec82ad2d16ed.

I'll take a look at the Herald behavior change. It will take me a few hours so please sit tight.

This explains how we prefer to write code:

Looks like a step in the right direction. Still doesn't explain Herald behavior change.

Also it's kind of strange to have orange badge (on commit list) for audit required status and blue exclamation mark (on commit detail page) at the same time.

blue is incorrect anyways. It doesn't make sense to have it mean both AUDIT_REQUIRED and AUDIT_NOTREQUIRED. I have a diff to correct all the colors into something more sensible.

In fact everything is connected. I've found, that blue exclamation mark next to auditor indicates, that audit is required (see https://github.com/phacility/phabricator/blob/master/src/applications/diffusion/controller/DiffusionCommitController.php#L1067-L1072) and dark exclamation mark next to auditor indicates that audit is requested (see https://github.com/phacility/phabricator/blob/master/src/applications/diffusion/controller/DiffusionCommitController.php#L1085-L1090).

One thing I haven't noticed from

I'm also curious about these exclamation mark icon colors next to auditor usernames in commit. I think badge color might be related to some in some way. Is there any documentation about Phabricator UI, e.g. what interface element means what?

Thanks, these offhand look incorrect to me too. cc @btrahan

A thought, as we prepare our Phabricator site to go public:

I'll second this. Been wondering for a while now, why we couldn't set up a public home page, but constantly had it defaulting to the login. Spent quite a while hunting through security setting before I finally figured out that there was one of the panels set to "All users" rather than public.

Support Impact This is generally a support-focused feature.

thx, T4863: Allow Workboard Cards to be customized for display would do the trick if blocking and blocked task id caould be added as a custom field to cards.

Going to merge it over so we'll have this information on that ticket.

The personal workboards is the more interesting task, it would independent and let you organize just your work without disrupting a Project's board.

It's an interesting idea, but it has issues since we'd no longer have a single vision of a board or column. We generally expect Dashboards do the heavy lifting when it comes to providing you with your view of your workload. Additional tasks that might interest you:

We should probably roll this into T4103 and let admins define an 'anonymous' homepage and default 'user' homepage.

As anonymous user, visit https://phab-01.wmflabs.org/

We don't plan to pursue the proposed behavior because it's confusing (different users get dramatically different views of the same dashboard, and it's not obvious why). Can you explain your use case for this?

• We should probably write a new edge (PanelHasChildPanel or similar) and show "this panel is embedded in other panels: ..." rather than trying to write the dashboard edge to all children.
• Only the tab panel is affected for the moment.
• The "This panel does not appear on any dashboards." message should be tailored.

This is technically true in a very indirect sense, but not very user-friendly or helpful.

✘ Merged into T5487.