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.
- Start the instance onboarding
- Create super admin users
- 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)
- After the sync occurs, you'll see the users are creating duplicated
User to be created according to the current user creation logic, and not to be duplicated.
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.
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
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.
Restart the Jira Connector