Issue Summary

      Jira 10.3.2 Synchronization process of Repositories on Gitlab DVCS accounts, shows failed due to the next error:

      java.lang.NullPointerException: Cannot invoke "com.atlassian.jira.plugins.dvcs.gitlab.api.model.GitLabUser.getUsername()" because "user" is null
      ...
      

      The impact of this, is that mark the synchronization of repositories as Failed.

      In the previous version 9.12, this was a message saying "User could not be found".

      Steps to Reproduce

      1. On Jira:
        • Spin an instance.
        • Create a dummy sample environment, such as Scrum
        • Check one ticket key for reference "SCRUM-9"
      2. On Gitlab:
        • Create a user as reporter "User A"
        • Make this "User A" owner of a group and a project.
        • Make a commit with "User A", referring to this ticket "SCRUM-9"
        • Create a user as reported "User B"
        • Make a commit with "User B", referring to this ticket "SCRUM-9"
        • With "User A", make all the approvals and merge requests.
        • Proceed to link Jira and Gitlab, for reference How to integrate Gitlab with Jira
          • Add the application Jira in Gitlab
          • Create the Application link in Jira
          • Create the DVCS account.
            •  Key point... when creating this, do it in Incognito mode, so gitlab requests for authorization.
            • On the authorization use the "User B" credentials.
      3. On Jira
        • Once the DVCS account is there, do a FULL SYNC.

      Expected Results

      the sync should be able to be done, with the limitation of fetching what the user that authorize is allowed to see.

      Actual Results

      The sync is marked as Failed

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

          Form Name

            [JSWSERVER-26321] Synchronization of Gitlab DVCS accounts failing due to User is null

            There are no comments yet on this issue.

              Unassigned Unassigned
              d001924c850a Francisco Crespo Smith
              Affected customers:
              0 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated: