Creator of new project does not get owner privileges
Problem
When a user creates a project in group in which he has master privileges he does not get owner privileges for the new project. Is that intentional? That implies that projects created in the group can only be deleted by group owners but not by the user who created the project originally.
Proposal
We follow a similar pattern as for subgroups. We want to be as consistent as possible between groups and projects moving forward.
- This behaviour is controlled as it is for subgroups. This setting defines whether or not a developer should be able to create projects in the first place.
-
DEVELOPERS
who are allowed to create projects becomeOWNER
of the project upon creation. An explicit membership record is created. - If the
DEVELOPER
is downgraded in the ancestor groups, they remainOWNER
of the project. - If the
DEVELOPER
is removed from the ancestor groups, the optionAlso remove direct user membership from subgroups and projects
will have to be explicitly checked to remove theOWNER
from the project as well
Due to security, financial and operational concerns, we will look into Prevent OWNERS from inviting external members (#381452) before taking up work on this issue.
Edited by Christina Lohr