GitLab Jira Integration with Jira Login URL ?nosso
Summary
Customer is using Jira instance setup with Azure Authentication for the user login. However, GitLab needs to login in JIRA with a nosso
parameter. As a result, the "Web URL" is "https://<jira_server>/?nosso" while the "Jira API URL" is "https://<jira_server>".
The problem is that all URLs constructed by GitLab contain the extra parameter in the wrong place and are effectively unusable... e.g. "https://<jira_server>/?nosso/browse/TICKET-XXXX"
Issue reported by a Starter Customer (Internal ticket)
Steps to reproduce
- Set up Jira with SSO login and enable nosso.
- Set up GitLab Jira Integration - Paste nosso in Web URL
- Click any link to Jira issues on GitLab.
- Gets directed to "https://<jira_server>/?nosso/browse/TICKET-XXXX"
Example Project
What is the current bug behavior?
Jira links directed to "https://<jira_server>/?nosso/browse/TICKET-XXXX" instead of the correct URL: "https://<jira_server>/browse/TICKET-XXXX"
What is the expected correct behavior?
Jira URLs should point to "https://<jira_server>/?nosso/browse/TICKET-XXXX"
Relevant logs and/or screenshots
Output of checks
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`)
GitLab v13.9.3
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
Add a new field for Jira Login URL