Merge Requests broken when forked project has them disabled

Hi Guys,

i don't think this behavior is intentional. On our local GitLab EE instance (CE is also affected) Merge Requests are disabled in new projects by default to keep it simple for new users. This leads to the following (Also reproduced on gitlab.com):

  • Fork project Namespace_A/Project_A to create forked project Namespace_B/Project_A.
  • Disable Merge Requests in Namespace_B/Project_A.
  • Make some changes in Namespace_B/Project_A.
  • Navigate to Namespace_A/Project_A -> Merge Requests.
  • Click New Merge Request (Which points to Namespace_B/Project_A/merge_requests/new - and seems to be wrong)
  • Enjoy the HTTP 404

Enabling the Merge Requests in the forked project solves the issue. But as mentioned, we got them disabled by default.

Any ideas? Am i doing something wrong?

Br, Thomas

Edited Jun 19, 2025 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading