<!--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=225929) </details> <!--IssueSummary end--> <!-- The first four sections: "Problem to solve", "Intended users", "User experience goal", and "Proposal", are strongly recommended, while the rest of the sections can be filled out during the problem validation or breakdown phase. However, keep in mind that providing complete and relevant information early helps our product team validate the problem and start working on a solution. --> ### Problem to solve <!-- What problem do we solve? Try to define the who/what/why of the opportunity as a user story. For example, "As a (who), I want (what), so I can (why/value)." --> Now, all issue's labels are copied to their merge requests. Sometimes it's not convenient for special workflows. There are a few teams that remove all labels for new merge requests. They have to clean labels either via web UI setting "No Label" option *(in the Labels drop-down list)* or via API *(webhooks, shell scripts, etc.)* ### Intended users Developers, Product Managers ### User experience goal <!-- What is the single user experience workflow this problem addresses? For example, "The user should be able to use the UI/API/.gitlab-ci.yml with GitLab to <perform a specific task>" https://about.gitlab.com/handbook/engineering/ux/ux-research-training/user-story-mapping/ --> The user should be able to use Project Setting to choose what is the default behavior for new merge request *(checkbox "with issue labels" or "without labels at all")* Also, I'd like to have [Push option](https://docs.gitlab.com/ee/user/project/push_options.html#push-options-for-merge-requests) for removing labels from MR. ### Proposal <!-- How are we going to solve the problem? Try to include the user journey! https://about.gitlab.com/handbook/journeys/#user-journey --> Add one more additional checkbox into "Merge requests" section of General project setting:  ### Further details <!-- Include use cases, benefits, goals, or any other details that will help us understand the problem better. --> I create merge requests via push options, and I don't want to waste time deleting labels via Web UI or API ### Permissions and Security Don't know ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/workflow.html#for-a-product-change * Add all known Documentation Requirements in this section. See https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements * If this feature requires changing permissions, update the permissions document. See https://docs.gitlab.com/ee/user/permissions.html --> Don't know ### Availability & Testing <!-- This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier. What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance. * Unit test changes * Integration test changes * End-to-end test change See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-planning --> Don't know ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> We put this option and when we create new merge request *(via Web UI and API)* - it has no labels. ### What is the type of buyer? Don't know ### Is this a cross-stage feature? Don't know ### Links / references https://docs.gitlab.com/ee/user/project/settings/#merge-request-settings https://docs.gitlab.com/ee/user/project/push_options.html#push-options-for-merge-requests