Have Project Settings included in Project Templates
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
I want to be able to create custom project templates to enable consistency. For example, having a consistent maximum file size for pushes or consistent set of 3rd party integrations (e.g. JIRA) made available to team members, via a set of settings baked into a project template, would be helpful to avoid duplication in project setup and configuration. It can also serve as a vehicle to enforce certain conventions across the group or organization.
Intended users
Anyone who creates projects within an organization.
User experience goal
Enable the user to avoid repeatedly configuring multiple projects with the same group of settings.
Proposal
Under the Settings tab for a GitLab project (let's call it Project A), there are a number of things that can be configured. Each setting could have perhaps have a toggle or switch that enables it to be included among a set of settings that are duplicated whenever a new GitLab project is created from a template (e.g. Push Rules or Project Visibility or something else). So we could update a bunch of settings in Project A, then have Project A be used as a template. We could create a new project that inherits these settings from Project A.