Issues from a Customer Issue Tracker from the same GitLab instance should reference automatically

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Summary

Using another project as an issue tracker is useful when combining several projects' issues in one location.

It can work like so:

Group - Issues enabled

  • Project 1 - Issues disabled / Customer issue tracker set to Group
  • Project 2 - Issues disabled / Customer issue tracker set to Group

This works well, however the automatic referencing in Merge Requests does not work correctly.

Writing Closes #2, does not link to the Issue#2 from the Groups' issue tracker, even though the user & project has access to it. However, if you paste the full URL then it does work, i.e Closes https://url-to-issue.

Steps to reproduce

  • Set up a project to be the issue tracker.
  • Set up another project, disable it's issues, set up a Custom Issue Tracker as the first projects issues.

Example Project

What is the current bug behavior?

References in Merge Requests don't automatically reference the Customer Issue Tracker set up for the project. The customer issue tracker is a GitLab project in the same GitLab instance.

What is the expected correct behavior?

Since the issue tracker project is in the same GitLab instance, and the user and project have permissions for it, the issues should be referenced correctly in merge requests.

Closes #2 should close the Issues#2 from the issue tracker.

Relevant logs and/or screenshots

I stepped through the GDK and I think this is because project.external_references_supported? is returning false.

This is false in the Integrations::Base::IssueTracker#support_cross_reference?. If I set that to true then it works.

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info 

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)


(we will only investigate if the tests are passing)

Possible fixes

Edited by 🤖 GitLab Bot 🤖