Enforce project creation from group or instance templates

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Problem to solve

Many organisations use instance / group project templates to pre-configure a project in such a way that it adheres to company standards (these may include push rules, MR approval rules, link to external .gitlab-ci.yml, protected branches, etc, etc.) as well CODEOWNERS file in the repo to set default code ownership.

At the moment users creating new projects have full freedom in how the project is created (blank, from an instance or group templates, import from an external repo. And it is very simple to 'default' into creation of a blank project. A good improvement would be to enforce project creation from specific set of templates. In this manner all NEW projects will be default be in compliance with company policies.

Intended users

• Delaney (Development Team Lead)
• Sasha (Software Developer)
• Devon (DevOps Engineer)

Proposal

In the instance and group level introduce new setting under templates that would limit how projects can be created.

Modify the flow of creating a new project to account for the limitation.

New project screen	Create from Template

Prevent users from getting stuck

• Do not allow limitation if no templates are specified
• Prevent users from deleting the last template

Permissions and Security

🤝 Cross-group collaboration

• Responsible groupcompliance
• Consulted, Accountable groupimport

Documentation

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

GitLab Ultimate

This is a way for orgs to automate their compliance as well as enforce workflows, which is why it would go inside GitLab Ultimate as opposed to another tier.

Links / references

Enterprise customer interested in this feature: https://gitlab.my.salesforce.com/00161000015M5I8