jira_auth_type required for Jira Integration Resource
Summary
jira_auth_type is required but not marked as required in documentation when configuring Jira Integration
Steps to reproduce
Use the Setup Jira Issues REST Resource to configure Jira Integration.
In our case we pass url, username, password, active, commit_events, and merge_request_events.
Example Project
What is the current bug behavior?
When we make the request we get the following back:
Server responded with code 400, message: jira_auth_type is missing. Request URI: https://gitlab.com/api/v4/projects/XXXXXXXX/services/jira (Gitlab::Error::BadRequest)What is the expected correct behavior?
According to the documentation jira_auth_type is not a required field, so it's omission should default to using Basic auth, as it did in previous versions of GitLab.
Relevant logs and/or screenshots
Output of checks
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)