"Another issue tracker is already in use..." error activating JIRA issue tracker.
Summary
"Another issue tracker is already in use..." error activating JIRA issue tracker. No other services are active in the project.
See: https://gitlab.com/gitlab-org/gitlab-ce/issues/22797
Steps to reproduce
GitLab Community Edition 9.4.3
We deleted a custom webhook issue tracker on a project, and defined a JIRA service integration on the project. The JIRA integration was originally created as inactive, and I am trying to activate the service now.
When I press the "Test settings and save changes" button, I get:
"Another issue tracker is already in use. Only one issue tracker service can be active at a time" error.
There are no other active issue trackers for that project. Other services (HipChat and SlackNotifications) display "Last edit" date in the project services list.
Example Project
What is the current bug behavior?
"Another issue tracker is already in use. Only one issue tracker service can be active at a time" error sent when activating an issue tracker on a project.
What is the expected correct behavior?
The JIRA issue tracker should be enabled.
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
)
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)