Jira integration wrongly sets assignee

Summary

When linking to a Jira issue in a Gitlab MR as Closes <issue_reference>, upon merging, Gitlab will change the assignee of that Jira issue while this is unwanted.

This has been happening only recently. I'm not sure since what version upgrade, but we've been having the Jira integration setup for months and it has only been since a few days/weeks we noticed this. We keep up with the latest Gitlab releases about as soon as a patch release is available (e.g. 10.5.x), so it's got to be the either the latest 10.5 or the 10.4 before that which is causing the issue. Configuration on Jira has not been changed in a long while.

This is a pretty annoying issue for our administration to keep track of who does what work as our Jira assignees are deleted, so please fix this asap.

Steps to reproduce

Link Gitlab project with Jira integration. Create a merge request with an 'action' reference (closes / fixes / ...) to the issue. Merge the MR. The Assignee of the Jira issue will be set by the (in our case called) Gitlab User user.

Example Project

What is the current bug behavior?

The assignee of the Jira issue gets set to Gitlab User in addition to the status change.

What is the expected correct behavior?

Only the status should be updated.

Relevant logs and/or screenshots

Example of occurence:

On the part of Gitlab: gitlab

Jira issue after MR is merged: jira

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info 
System information
System:		Debian 8.10
Proxy:		no
Current User:	git
Using RVM:	no
Ruby Version:	2.3.6p384
Gem Version:	2.6.13
Bundler Version:1.13.7
Rake Version:	12.3.0
Redis Version:	3.2.11
Git Version:	2.14.3
Sidekiq Version:5.0.5
Go Version:	unknown

GitLab information
Version:	10.5.2-ee
Revision:	3834bbe
Directory:	/opt/gitlab/embedded/service/gitlab-rails
DB Adapter:	postgresql
DB Version:	9.6.5
URL:		https://*****
HTTP Clone URL:	https:///some-group/some-project.git
SSH Clone URL:	git@:some-group/some-project.git
Elasticsearch:	yes
Geo:		no
Using LDAP:	no
Using Omniauth:	yes
Omniauth Providers: google_oauth2, bitbucket


GitLab Shell
Version:	6.0.3
Repository storage paths:
  • default: /var/opt/gitlab/git-data/repositories Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks Git: /opt/gitlab/embedded/bin/git

Results of GitLab application Check

Expand for output related to the GitLab application check 
Checking GitLab Shell ...

GitLab Shell version >= 6.0.3 ? ... OK (6.0.3)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by git:root, or git:git?
default... yes
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ...
4/2 ... ok
4/3 ... ok
4/5 ... ok
4/7 ... ok
4/8 ... ok
4/9 ... ok
4/10 ... ok
4/11 ... ok
4/12 ... ok
4/13 ... ok
4/14 ... ok
4/15 ... ok
4/16 ... ok
4/17 ... ok
4/18 ... ok
4/19 ... ok
4/20 ... ok
4/21 ... ok
4/22 ... ok
4/23 ... ok
4/24 ... ok
4/25 ... ok
4/26 ... ok
4/28 ... ok
4/29 ... ok
4/30 ... ok
4/32 ... ok
4/36 ... ok
4/38 ... ok
16/39 ... ok
4/40 ... ok
4/42 ... ok
4/43 ... ok
4/44 ... ok
4/45 ... ok
4/47 ... ok
4/48 ... ok
4/49 ... ok
4/50 ... ok
4/51 ... ok
4/52 ... ok
4/53 ... ok
4/54 ... ok
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Redis available via internal API: OK


Access to /var/opt/gitlab/.ssh/authorized_keys: OK
gitlab-shell self-check successful


Checking GitLab Shell ... Finished


Checking Sidekiq ...


Running? ... yes
Number of Sidekiq processes ... 1


Checking Sidekiq ... Finished


Reply by email is disabled in config/gitlab.yml
Checking LDAP ...


LDAP is disabled in config/gitlab.yml


Checking LDAP ... Finished


Checking GitLab ...


Git configured correctly? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config up to date? ... yes
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory exists? ... yes
Uploads directory has correct permissions? ... yes
Uploads directory tmp has correct permissions? ... yes
Init script exists? ... skipped (omnibus-gitlab has no init script)
Init script up-to-date? ... skipped (omnibus-gitlab has no init script)
Projects have namespace: ...
4/2 ... yes
4/3 ... yes
4/5 ... yes
4/7 ... yes
4/8 ... yes
4/9 ... yes
4/10 ... yes
4/11 ... yes
4/12 ... yes
4/13 ... yes
4/14 ... yes
4/15 ... yes
4/16 ... yes
4/17 ... yes
4/18 ... yes
4/19 ... yes
4/20 ... yes
4/21 ... yes
4/22 ... yes
4/23 ... yes
4/24 ... yes
4/25 ... yes
4/26 ... yes
4/28 ... yes
4/29 ... yes
4/30 ... yes
4/32 ... yes
4/36 ... yes
4/38 ... yes
16/39 ... yes
4/40 ... yes
4/42 ... yes
4/43 ... yes
4/44 ... yes
4/45 ... yes
4/47 ... yes
4/48 ... yes
4/49 ... yes
4/50 ... yes
4/51 ... yes
4/52 ... yes
4/53 ... yes
4/54 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.5 ? ... yes (2.3.6)
Git version >= 2.9.5 ? ... yes (2.14.3)
Git user has default SSH configuration? ... no
Try fixing it:
mkdir ~/gitlab-check-backup-1520960799
sudo mv /var/opt/gitlab/.ssh/id_rsa.pub ~/gitlab-check-backup-1520960799
sudo mv /var/opt/gitlab/.ssh/id_rsa ~/gitlab-check-backup-1520960799
For more information see:
doc/ssh/README.md in section "SSH on the GitLab server"
Please fix the error above and rerun the checks.
Active users: ... 16
Elasticsearch version 5.1 - 5.5? ... yes (5.2.2)


Checking GitLab ... Finished

Possible fixes

No

Edited by Mathieu Hinderyckx