It sounds like the issue of Jira creating two users, one with an email ID and the other with a company ID, might stem from user management configurations. Here are a few potential reasons based on context and general knowledge:
User Aliases/Multiple Directories: If user aliases or multiple directory configurations are used, duplication can happen. This aligns with the scenario where users have different usernames for different applications, such as Jira and Confluence. When integrating with tools like Crowd for centralized user management, it's essential to ensure that each user is uniquely identified across systems to prevent duplications
Sync Issues with LDAP or External Directories: If Jira is integrated with LDAP or another external directory service, synchronization issues may result in user duplications. For instance, if the mapping between users' email IDs and company IDs is not correctly configured, it may create separate accounts
Migration from Internal to External Management: Transitioning user management from Jira’s internal system to an external system such as Crowd or LDAP might lead to duplicate entries if the synchronization process does not cleanly map existing users
Ensuring consistent user identifiers and carefully configuring directory synchronization settings can help avoid such duplication. If the problem persists, reviewing the specific user synchronization logs and addressing any mismatches would be a prudent next step.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.