I want to be able to see every user that has access to my phabricator install. Ideally I'd like to be able to see all non-bot non-disabled users specifically.

@avivey that was my original proposal by I think @chad didn't like it.

actually, I misunderstood, the output, sorry about that.

(1) Some reference to "commit ranges" would have been nice. I had no idea what to search for to find that page
(2) thanks

I just tried to repro on a clean firefox profile and was unable to do so. Its either an edge case or something in my environment. Sorry for the noise.

It is fully reproducible for every user for me, including for myself.

Ah, I see. In that case, this task should morph to: inform the user, when in "management" mode that one of the panels may cause the whole dashboard to be unviewable.

In this case you *do* have access (to the dashboard, and to all the other panels) to everything but a single panel. Just that one panel should disappear.

This may be related, but is a little more specific: right now adding a private panel to the dashboard makes the whole thing go private. IMHO it should render, but without the panel the user can't see.

This particular issue is something I'm running into on the test install, before enabling it in production.

A big banner is totally fine by me. I just proposed an action menu item since it seems simpler.

So there are two workflows which are annnoying, and one general UI issue.

I would guess this is not an uncommon setup: many LDAP instances have self-signed certificates. Without this knob many standard LDAP setups would not work.

thanks!

thanks!

Some of the uses cases would be solved by the "bind projects to external things" request, but not all of them.

Note: this isn't a duplicate of T7969:

I think that use case is quite different: spaces provides some very high level isolation between various groups of users. These uses cases relate to projects/tasks/etc. within the same space.

There are a few problems or use cases that would be solved by this:

FWIW this allows key channels to work, although it is obviously not ideal:

One thing to note here: it would be nice to be able to define group membership based on other external things beyond just LDAP

• having a specific email address
• the output of an arbitrary script

I actually want both of those tasks.

FWIW, rebindablity is not required for my usecase, although I could see usecases for it.

I totally understand that, and agree with that notion. This is one of the reasons I like phabricator so much compared to other tools.

If I understand how hashtags are used for projects, than pretty much yes.

There are two use cases where this is still helpful: when talking about the task on a mailing list or otherwise outside of phabricator, when cross referencing tasks or projects on the other pages. The goal here is to provide an easily referencable object / task / bug / project: not just for pure organization.

ah, perfect. thanks!