Failure when importing issues from Jira

Summary

Importing issues from Jira Server through the GitLab Jira issue importer fails with "There was an error importing the Jira project".

"exception.message":"missing keyword: users_mapping"

Caught by the new Jira issue import spec here https://gitlab.com/gitlab-org/gitlab-qa-mirror/-/jobs/618145710

Steps to reproduce

To run the test on local against GDK, follow these steps:

  1. Increase the memory of you Docker for desktop to 7 GB and start JIRA in docker: docker run
    --publish 8080:8080
    --name jira
    registry.gitlab.com/gitlab-org/gitlab-qa/jira-gitlab:8.8-project-and-issue
  2. Start you GDK: gdk start
  3. From /qa directory, run: JIRA_ADMIN_USERNAME="<admin_username>" JIRA_ADMIN_PASSWORD='<admin_password>' CHROME_HEADLESS=false bin/qa Test::Instance::All http://localhost:3000 -- qa/specs/features/browser_ui/3_create/jira/jira_basic_integration_spec.rb --tag orchestrated Values for JIRA_ADMIN_USERNAME and JIRA_ADMIN_PASSWORD are in 1Password in the GitLab-QA Vault.

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

{"severity":"ERROR","time":"2020-06-30T18:05:46.858Z","correlation_id":"JULEKDbzaS8","tags.correlation_id":"JULEKDbzaS8","tags.locale":"en","exception.class":"ArgumentError","exception.message":"missing keyword: users_mapping","exception.backtrace":["app/graphql/mutations/jira_import/start.rb:29:in `resolve'","lib/gitlab/graphql/generic_tracing.rb:40:in `with_labkit_tracing'","lib/gitlab/graphql/generic_tracing.rb:30:in `platform_trace'","lib/gitlab/graphql/generic_tracing.rb:40:in `with_labkit_tracing'","lib/gitlab/graphql/generic_tracing.rb:30:in `platform_trace'","lib/gitlab/graphql/generic_tracing.rb:40:in `with_labkit_tracing'","lib/gitlab/graphql/generic_tracing.rb:30:in `platform_trace'","app/graphql/gitlab_schema.rb:41:in `multiplex'","app/controllers/graphql_controller.rb:58:in `execute_multiplex'","app/controllers/graphql_controller.rb:30:in `execute'","ee/lib/gitlab/ip_address_state.rb:10:in `with'","ee/app/controllers/ee/application_controller.rb:44:in `set_current_ip_address'","app/controllers/application_controller.rb:490:in `set_current_admin'","lib/gitlab/session.rb:11:in `with_session'","app/controllers/application_controller.rb:481:in `set_session_storage'","app/controllers/application_controller.rb:475:in `set_locale'","lib/gitlab/error_tracking.rb:51:in `with_context'","app/controllers/application_controller.rb:540:in `sentry_context'","app/controllers/application_controller.rb:468:in `block in set_current_context'","lib/gitlab/application_context.rb:52:in `block in use'","lib/gitlab/application_context.rb:52:in `use'","lib/gitlab/application_context.rb:20:in `with_context'","app/controllers/application_controller.rb:461:in `set_current_context'","ee/lib/gitlab/jira/middleware.rb:19:in `call'"]}

Screenshot: Screen_Shot_2020-06-30_at_3.09.29_PM

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)

Possibly caused by !34609 (merged)

Edited by Désirée Chevalier