<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=551502) </details> <!--IssueSummary end--> <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### 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](https://docs.gitlab.com/user/group/custom_project_templates/#what-is-copied-from-the-templates), 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 <!-- Label reminders Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->