DVCS connector updated Jira Server with wrong user

Summary

A project is setup to use the DVCS connector. After a merge request is reviewed and merged by the reviewer, user A, Jira Server updated the issue with the message:

Issue was automatically transitioned when <username of user Z> merged pull request `#1` in GitLab.

• User A and User Z have the same first name
• User Z is not a member of any GitLab.com project/groups that has the integration set
• User Z is not a part of the group organization

Steps to reproduce

Example Project

Affected customer:

• https://gitlab.zendesk.com/agent/tickets/198555 (internal)

What is the current bug behavior?

The Jira integration updated Jira cloud with wrong username.

What is the expected correct behavior?

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)

Possible fixes