JIRA DVCS Error Retrieving Repositories from Personal Namespace

Summary

Setting up JIRA DVCS with a GitLab personal namespace results in the error Failed adding the account: [Error retrieving list of repositories].

If you click "Try Again", an error Account is already integrated with JIRA. appears. The integration is activated, but no GitLab repositories are displayed in JIRA's DVCS admin view.

@ronkoster reported this issue and his account is on the Gold plan. I was also able to reproduce this with my nhxnguyen account which is on the Gold plan. Ron was able to successfully set up the connection for a different group namespace of his that is on Gold. So this issue appears to affect personal namespaces specifically.

Ron also noted that the integration was working for him as recently as the 12.3 release.

Steps to reproduce

Follow the GitLab JIRA Development Panel Integration setup instructions.

What is the current bug behavior?

JIRA displays the error message Failed adding the account: [Error retrieving list of repositories] and does not sync any repositories.

What is the expected correct behavior?

Repositories should be successfully pulled in and displayed in the JIRA DVCS admin.

Relevant logs and/or screenshots

Output of checks

(If you are reporting a bug on GitLab.com, write: This bug happens 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

(If you can, link to the line of code that might be responsible for the problem)