Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #9704

Closed
Open
Created Oct 07, 2015 by Administrator@rootOwner

MR with fork can mess up upstream project's issues

Created by: roboogle

Summary

Accepting MR involving forked project, may wrongly close issues in upstream project.

Steps to reproduce

Suppose you have project P1 and fork a project P2 out of P1: P1 is upstream, P2 is fork.

Now you work on P2, and fix issue #1 with a commit C1 whose message contains Fixes #1. Then open a MR of P2 into P1, containing commit C1. Accepting the MR, will correctly close P2#1, but will also close P1#1 which is wrong as it may be a completely unrelated issue.

Expected behaviour

Wrt the previous example, when accepting MR, issue P2#1 shall be closed, and issue P1#1 shall be not closed.

Assignee
Assign to
Time tracking