Please provide a setting to make it a requirement that Merge Requests are linked to an Issue before they can be merged
Proposal
Hello, we would like to make it a requirement on Merge Requests that an issue must be linked before it can be merged.
We are aware of the cross-linking feature for linking a Merge Request with an Issue: https://docs.gitlab.com/ee/user/project/issues/crosslinking_issues.html, however there does not appear to be a way to make the linking a requirement before a Merge Request can be merged. We are requesting the ability to make this a requirement.
Having issues linked is great, but if we can't require it for our developers, then it becomes difficult to track down what issue a merge request was associated with after the fact, and makes providing documentation and justification when a change is called into question, more tedious.
We would like to be able to apply this type of requirement at the project, group and namespace levels on gitlab.com. I can also foresee that self-hosted Gitlab users may want to be able to do the same across their entire instance; though being a SaaS user myself, I don't know how much demand there might be for this, so I request any self-hosted users to add their feedback in the comments.