15.10.1-ee - Selector for "instance template repository" behaves inconsitently

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

Summary

Steps to reproduce

Assume you have this repository structure and that “repositoryBAB” contained your issue templates.

- groupA
-- repositoryAA
-- repositoryAB
- groupB
-- subgroupBA
--- repositoryBAA
--- repositoryBAB
-- subgroupBB
-- repositoryBA
-- repositoryBB
  • Usage in groupA is no problem, “repositoryBAB” can be selected as “template repository”.
  • The problem arises when groupB tries to use the repository, as it is not selectable - only “repositoryBA” and “repositoryBB” are available.
  • For “subgroupBA” both repositories below it are available (“repositoryBAA” and “repositoryBAB”) but no repositories outside of it.

Example Project

What is the current bug behavior?

Not all repositories in the Gitlab instance are selectable

What is the expected correct behavior?

  • any accessible repository is selectable
  • the conditions for a repository to be selectable are documented

Relevant logs and/or screenshots

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 🤖