Include "Target Branch Workflow" settings in project templates/project exports
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Proposal
Summary
Target Branch Workflow settings should be included when creating a new project from a template or when exporting/importing a project.
Problem
Currently, when creating a new project from a template or exporting/importing a project, the Target Branch Workflow settings (from a project's "Settings" -> "Merge Requests" -> "Merge request branch workflow") are not copied over. This requires manual reconfiguration of these settings for each new project, which is time-consuming and error-prone for teams that standardize on specific workflow configurations.
Proposed Solution
Include Target Branch Workflow settings in the following operations:
- Project templates: When creating a new project from a template, copy the template's Target Branch Workflow configuration
- Project export/import: Include Target Branch Workflow settings in the exported project data and restore them during import
Based on the documentation, both creating a new project and exporting a project would seem to use the same codebase.
Benefits
- Reduces manual configuration overhead for new projects
- Ensures consistency across projects using the same template
- Improves team productivity and reduces setup errors
- Maintains workflow standardization across project migrations