Inactive account is shown due to directory order

Problem

Organizations using Jira with multiple subdomains often encounter issues when users change departments. When a user switches departments, their old account in the previous subdomain is deactivated, and a new account is created in the new subdomain with the same username. However, during synchronization with Jira, it sometimes displays the old, inactive account, leading to confusion and potential access issues.

Suggested Solution

Introduce a feature in Jira that prioritizes active accounts over inactive ones during synchronization, even if the active account resides in a lower order subdomain. Essentially, when Jira encounters two accounts with the same username across different subdomains, it should give precedence to the account that's active.

Why This Is Important

This feature is crucial as it can significantly improve user management in Jira, especially for organizations with a complex structure of multiple subdomains. It will reduce the confusion caused by displaying deactivated accounts and make the process of switching departments smoother for users. It will also reduce the administrative overhead of manually modifying connector orders or performing cleanup activities.

Workaround

Currently, the workaround involves modifying the LDAP setup to return only active accounts when queried and configuring Jira's User Directory to connect to this modified LDAP view. However, this workaround has its limitations and depends heavily on the capabilities of the LDAP server. Moreover, it may not be feasible for all organizations due to the complexity involved. Thus, a native solution within Jira would be highly beneficial.