Only projects in top-level namespace are available for adding via the toolchain feature within Jira Cloud

Summary

When attempting to add a code repository via the toolchain feature within Jira Cloud only projects in the top level namespace in GitLab are available for selection.

Projects within subgroups are not listed.

Steps to reproduce

Gitlab:

  1. Create a top level namespace
  2. Create a project within the top level namespace
  3. Create a subgroup within the top level namespace
  4. Create a project within the subgroup

Jira

  1. Create a new project
  2. Integrate gitlab with Jira
  3. Enable code for the project
  4. Link repositories using the toolchain feature

Note that the within the "Add code repository" dialog when attempting to link the repository

  • if you select the top level namespace the project created previously is listed
  • if you select the subgroup the project created previously is not listed

Workaround

  1. Move the project to the top level namespace
  2. Link repositories using the toolchain feature in Jira
  3. Move the project to the subgroup

Example Project

What is the current bug behavior?

Unable to select a project that resides in a subgroup from the "Add code repository" dialog when attempting to link the repository using the Jira toolchain feature

What is the expected correct behavior?

Projects that resides in a subgroup should be listed and selectable from the "Add code repository" dialog when attempting to link the repository using the Jira toolchain feature

Relevant logs and/or screenshots

Output of checks

This bug happens on GitLab.com reproduced on GitLab.com

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

This issue is being addressed by Atlassian in https://jira.atlassian.com/browse/JSWCLOUD-23744.

Edited by Grant Hickman