Hi! Can you please let us know what version of Phabricator you're running?

See Contributing Bug Reports for some help with getting versions and other information we need, or I can walk you through how to give us this information if you aren't sure. Thanks!

Yeah, running a version from Friday: 5eecff91cdd3

Great, thanks!

I'm having trouble reproducing this. I tried to follow the instructions you provided to recreate the issue, but didn't seem to experience it. Here's what I did.

First, I navigated to a subproject:

Note that "Accelerate Dogs" is a subproject of "A Parent Project", and that I am currently not a member.

Next, I clicked "Join Project" to join the project:

I confirmed this dialog, and this screen loaded:

Note that the members list now shows me ("admin") as a member.

Do you have any ideas what I might be doing wrong in following your steps, or any extra information which might be missing?

Hmm, that looks like the same process.

Here's what it looks like for me:

I click Join Project and get this:

I'm an admin, so should be able to join any project

Also interesting:

That task in the project doesn't show the name of the project even though I'm an admin and a member of the parent

Note that being an administrator doesn't matter: administrators have no special privileges, and can not bypass policies. See:

https://secure.phabricator.com/book/phabricator/article/users/#administrators

Oh ok, so I guess that doesn't matter then

I just encountered the same error message.

1. I added the first subproject P-1 to one of our projects P, thereby moving all its members.
2. I used ./move_beneath.php --parent P --child P-2 --subproject --keep-members child (T10350)
3. I try to edit P-2, but see instead:

You do not have the required capability ("<extended>") to do whatever you are trying to do.
Users with the "<extended>" capability:

    This object has an unknown or invalid policy setting ("").

In the DB I see that P-2 has has viewPolicy: P and editPolicy: admin.

Is this the same issue, or shall I file a new bug?

What are the view, edit and join policies of the parent project set to?

From the DB: P has viewPolicy: P, editPolicy: admin, joinPolicy: admin.

In T10427#161230, @rbalik wrote:

Also interesting:

I can confirm that, too. On the P-2 profile page, I see:

Looks Like
    Restricted Project

But obviously I can access the profile page, see the members, etc.

What might be related: I am a member of subproject P-1, which has viewPolicy: P, editPolicy: admin, joinPolicy: admin. So the policy is kind of recursive.

I can't make a workboard either for the subproject. When I click "Create Workboard" it doesn't do anything

Hi guys, any update on this? It looks like I can't add members to the parent project either so subprojects seems to be making a mess of things at the moment.

Oh and we're at 31984a78ee at the moment. I may run an upgrade here in a bit just to see if the newer version fixes anything.
It looks like any project with subprojects has the "Add Member" link grayed out.

Upgraded to 121e68e3 and the problem is still there

The original error message seems to be improved, btw, but I also seem to have a zombie subproject now.

Note that I should be able to join this:

But I can't when I try:

I am a member of the hardware project.

Ok, I was able to join the subproject by setting permissions on the parent project to allow joining by "All Users"
I still can't add users to the parent project though

What is a "zombie" subproject and how can we reproduce this?

I was calling it a zombie because I couldn't join it or change any of the settings on it even though it said I had permissions to do so. Maybe not the best description.

I can reproduce this by making the parent project visible only to members (of which I am one)

I still can't add users to the parent project though

This is expected, parents users are the union of all subprojects. See https://secure.phabricator.com/book/phabricator/article/projects/#subprojects-and-mileston

Both subprojects are set to "All Users" for their permissions

I have also archived both subprojects in an attempt to workaround this and I still can't add users to the parent project.

Oh, I totally misunderstood what you said.

Ok, I was able to add the user to the project by adding him to one of the subprojects. I guess that works for us. Thanks for your help.

In T10427#161255, @urzds wrote:

I can confirm that, too.

This issue persists, though. it should be reproducible by using the conversion scripts. (s.a.)