Issue Summary

This is reproducible on Data Center: (no)

The customer is using Jira Cloud on Connector ID, but the service wrongly identifies it as Not Cloud, resulting in the wrong user mapping logic being applied - and duplicated users. 

Steps to Reproduce

1. Start the instance onboarding 
2. Create super admin users
3. Configure the sync, and create a new story in Jira - assign it to a user that already exists in Jira Align (one of the Super Admin you created in the previous step)
4. After the sync occurs, you'll see the users are creating duplicated

Expected Results

User to be created according to the current user creation logic, and not to be duplicated. 

Actual Results

The customer is using Jira Cloud on Connector ID, but the service wrongly identifies it as Not Cloud, resulting in the wrong user mapping logic being applied.

     ConnectorId: 1
     CorrelationId: 380405968
     Customer: xxxxxxxxxxxxx
     Event: IssueTimer
     JiraApiConnectionTest: true
     JiraServerinfo: {
         "baseUrl": "https://xxxxxxxxxxxxxdev.atlassian.net",
         "version": "1001.0.0-SNAPSHOT",
         "versionNumbers":
         [
             1001,
             0,
             0
         ],
         "deploymentType": "Cloud",

See that the Connector is set to Cloud = False hence using the Jira Onprem logic - /rest/api/2/user?username= - as outlined here https://hello.atlassian.net/wiki/spaces/JALN/pages/1307007521/Process+Pull+Jira+User+Data+User+data+pull

   APIRequestUrl: /rest/api/2/user?username=ntKpWRFWrfBjgyuHPgbdX6cJLV7%2fApZVh%2bd51qY8vtQ%3d
     APIResource: rest/api/2/user
     APIResponseStatus: Completed
     APIResponseStatusCode: BadRequest
     APIResponseStatusCodeValue: 400
     APIResponseStatusValue: 1
     APIResponseTimeMilliseconds: 195.17440000000002
     Action: UserSync
     AuthType: OAuth
     Build: 10.111.3.20601
     ConnectorId: 1
     CorrelationId: 1149186832
     Customer: xxxxxxxxxxxxx
     Event: CustomTimer
     JiraCloud: false
     Method: RunUserSync

UpdateConnectorService_Starting method in AgileCraft_Jira.cs that updates the tblWMSConnector.version value. This method gets triggered in OnElapsedTimerServiceOnStart and * that is when a connector service is *started.

Workaround

Restart the Jira Connector