Hi Everyone, We are in an ambiguous situation that we have 100+ duplicate users coming from two different AD's from Crowd, those duplicate users usernames be like ex: twhite (AD 1 **old**) and twhite3 (AD 2 **new**) and we thought of converting all records like assignee, reporter etc from twhite to twhite3 manually or jira-python script, after converting records user would not see his old username i.e. twhite while start typing name in user picker field I was trying to disable/inactive user from crowd side but could not able to do that showing an error Note1: Removing or disabling the user from AD 1 **old** LDAP side will affect the user to use other applications and removing AD 1 **old** from the crowd is not possible at this moment because of management call. Note2: Those who have unique ID between both AD's not an issue. like tnaik (AD 1 **old**) and tnaik (AD 2 **new**) Any suggestions would be much helpful. Regards T

@Carlos Faddul Ok sure, I will check Atlassian support. Thanks

@Teja no luck =\ Maybe atlassian support for crowd, i don't have VM's of server anymore since february =(

@Carlos Faddul Any luck? Do you remember anything? Thanks

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to disable duplicate user from crowd?

Teja

Hi Everyone,

We are in an ambiguous situation that we have 100+ duplicate users coming from two different AD's from Crowd, those duplicate users usernames be like ex: twhite (AD 1 **old**) and twhite3 (AD 2 **new**) and we thought of converting all records like assignee, reporter etc from twhite to twhite3 manually or jira-python script, after converting records user would not see his old username i.e. twhite while start typing name in user picker field

User field.PNG

I was trying to disable/inactive user from crowd side but could not able to do that showing an error

Note1: Removing or disabling the user from AD 1 **old** LDAP side will affect the user to use other applications and removing AD 1 **old** from the crowd is not possible at this moment because of management call.