Not respecting selected namespace for new projecyt

Created by: bassrock

When I create a new project and select a different namespace the new project always reverts to the default namespace of the current user.

Created by: dzaporozhets

Can you please share more details. I was not able to reproduce it for me. In order to fix this one I need next info:

• GitLab revision
• Is your user is admin
• what namespace (user or group are you selecting)
• are you an owner of this group

By Administrator on 2012-12-27T09:29:46 (imported from GitLab)

Created by: hopson

I was confused by this as well; only the group owner can create a project.

Automatically assigning the new project to another group seems unintuitive - it might make more sense to 1) allow multiple group owners, 2) filter the "New Project" namespace list to include only allowed Namespaces, and/or 3) show an error when trying to add a project to a namespace you don't own.

By Administrator on 2012-12-31T18:56:54 (imported from GitLab)

Created by: yuters

+1 @hopson

and 4) Give an Admin user the possibility to create projects in every group.

The current situation seems to be that an Admin can't create a project in a group if he's not the group owner, but he can transfer it from his namespace to the group after.

By Administrator on 2012-12-31T20:17:38 (imported from GitLab)

Created by: bassrock

Yea the above all seems right. Only the group owner can create projects in their namespace but yet all the groups show up in the create project list and no error shows up when you select another

On Dec 31, 2012, at 12:12 PM, Martin Bastien notifications@github.com wrote:

+1 @hopson

and 4) Give an Admin user the possibility to create projects in every group.

The current situation seems to be that an Admin can't create a project in a group if he's not the group owner, but he can transfer it from it's namespace to the group after.

— Reply to this email directly or view it on GitHub.

By Administrator on 2012-12-31T20:17:39 (imported from GitLab)