<!--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=364646) </details> <!--IssueSummary end--> ### Proposal Before the Merge Request is merged the selection of a Milestone is expected. There is currently no option available to make selection of a Milestone mandatory. This requires manual checks and intervention potentially after the merge has been executed. ### Possible solution: For us an option would be to have a project Merge Requests Setting to define Milestone selection mandatoy yes/no (default). Since we don't require a Milestone to be set when creating a new Merge Request, the validation should **only** happen before starting to merge. **Merge must be prevented without a Milestone beeing selected.**