Jira issue import not working using Jira Server after switching to GraphQl
Summary
After updating the Jira importer to use graphql, MR here, importing issues from Jira Server is no longer working. (Importing from Jira Cloud should still work).
Previously, we'd use rest/v2/project
to get the list of projects from Jira but after the update to GraphQl, we're now using rest/v3/project/search
. The issue is that unlike Jira Cloud, Jira Server doesn't have the rest/v3/project/search
endpoint, just rest/v2/project
.
This was found in an MR that adds an e2e test for Jira issue imports: !32816 (comment 354752117)
Steps to reproduce
Example Project
(If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report)
(If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version)
What is the current bug behavior?
(What actually happens)
What is the expected correct behavior?
(What you should see instead)
Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.)
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)