Issue Summary

Pull Request in Jira display incorrect user as the Author when the actual Author is disabled in Gitlab.

Steps to Reproduce

1. Integrate Jira with GitLab by following the steps in Integrating Jira with GitLab documentation.
2. Create a new user in GitLab.
3. As the new user, create a new Merge Request in GitLab that is associated with a Jira Issue.
4. Ensure that the Pull Request in Jira is mapped to the correct AUTHOR (the new user).
5. Disable the new user in GitLab. Disabled user appear as "Blocked User" in Gitlab instead of the Full Name.
6. As an Admin in Gitlab, Edit the Merge Request created by the disabled user.
7. Verify if the Pull Request in Jira mapped to the actual AUTHOR.

Expected Results

Pull Request in Jira contain the correct Author:

Actual Results

The actual Author is still mapped correctly in the actual actual Merge Request in GitLab however, the Pull Request in Jira contain the incorrect Author:

The actual Author become the reviewer for the Pull Request in Jira:

Upon further inspection from Jira Database, the AUTHOR column inside AO_E8B6CC_PULL_REQUEST table is updated to a random GitLab user name after the user is disabled in GitLab causing the wrong mapping.

Workaround

Update the AUTHOR column with the actual Full Name of the disabled user:

UPDATE "AO_E8B6CC_PULL_REQUEST" SET "AUTHOR" = '<replace_with_gitlab_user_full_name>' where WHERE ID = <pull_request_id>;