@Citrix Devops
thanks for your response. see my response in line with your comments.
From my experience, you can rename users in LDAP or in Crowd and JIRA will pick them up (assuming that JIRA is connected to Crowd).
Yes, we expected it should work like that, but it is not, with earlier it was working like this, i suppose.

Still, the same operation will not work on Confluence, as it would confuse it badly.
yes, Confluence is not updating with user changes

Still, I do think that the the ability to merge users is not here and the hacks for implementing it are really ugly.
I read many users had issues with DB side hack, we need to have good scripts to change all of them good, otherwise it will corrupt data!!

@Mark Lassau
Thanks for your reply.
Yes you got it right, currently we use AD also for authentication connected thro crowd.

Answers to your Qs
Do you want to connect JIRA directly to AD or do you want JIRA connected to Crowd and Crowd gets user data from AD?
we want JIRA connected thro Crowd, crowd gets users from AD.
Do the usernames in AD match the current usernames in Crowd internal directory?
No, crowd internal users have different convention like - xx-fristname-lastname, AD has "yxxxxx" y - first letter of first name, xxxxx - last name
If usernames don't match, how many are different? Is there a simple rule for how to change them or are the changes "random"?
we have around 130 of them, which have same convention, they are not random. we can bulk change them, or one by one.

We want JIRA or Confluence issue history intact for Crowd internal users, when we merge user with AD.

Thanks
Raju

From my experience, you can rename users in LDAP or in Crowd and JIRA will pick them up (assuming that JIRA is connected to Crowd).

Still, the same operation will not work on Confluence, as it would confuse it badly.

Still, I do think that the the ability to merge users is not here and the hacks for implementing it are really ugly.

We do have to rename/merge users quite often because we do import data from other systems where users had different usernames and you inevitably end-up with having both the current user, with his content and the old user where you want to merge into the new one. So far we performed these at database level, really ugly.

radluru
If I understand then you currently have JIRA connected to Crowd and users are stored in a Crowd internal directory.
Now you want to change to having users coming from MS AD.
Same situation for Confluence.

Questions:

• Do you want to connect JIRA directly to AD or do you want JIRA connected to Crowd and Crowd gets user data from AD?
• Do the usernames in AD match the current usernames in Crowd internal directory?
• If usernames don't match, how many are different? Is there a simple rule for how to change them or are the changes "random"?

Hi Guys
can somebody help us for user mapping for our scenario.
JIRA v6.3.12 (recently upgrade from 6.2), Crowd 2.8.0( recently upgrade from 2.7.0) connects to MS AD, Confluence 5.6.5
DB- MS SQL 2012

JIRA --> Crowd < ----> MS AD
Internal Dir Internal Dir
people used their user ids from JIRA Internal Dir and Crowd Internal Dir and created issues in JIRA, now we want to map all those users to AD accounts.
Can above scripts will help me to map and change these users.

Same scenario for Confluence also, users created contect with their Crowd internal Ids, we want map them to AD user accounts, how can i do this.
Jamie disabled his rename and merge user from Script runner also!

In old Crowd 2.7, my colleague says he did rename user in crowd internal, it picked up AD user and merged, not sure about this, can somebody confirm this, if that is case, i can go back to crowd 2.7 and try that.
Appreciate your help.
Thanks

Hi guys, in case if someone needs updated script for renaming usernames in JIRA ~6.2.6 here it is. I've added only the tables we really needed to be updated, don't consider this any semi-official thing.

We are using v6.2.6. We tried editing the username and it worked. But unfortunately, past comments (where the user was mentioned) of the user we edited were not updated to the new one, it displays the previous username. Is this a current limitation?

edilberto.balanak
Sorry for late reply.

Your are correct - this is a limitation.
Because the "mentions" in comments are really just some formatting text inside a free form text field there is no easy way to rename all of these.
We would have to load up all comments (potentially millions) and parse the text / wiki markup and look for patterns like [~old-username] and edit these ...

que bizarrice! como é possível não poder renomear um usuário? Que tipode engenhoca foi construída?

1. se você criar um usuário, fazer dele líder de um projeto.
2. se você um dia renomear este usuário, o banco não atualiza.

qual o problema? é cache? nunca ouviu falar de cache flush?

como que resolve essa gororoba?

Sure - let's take this offline and over to Questions just so we don't spam everyone while we're figuring it out - we can post the 'fix' here when we're done. I'll post the question from your original post .... well, here's the link to your questions post:

https://answers.atlassian.com/questions/320093/asked-by-martin-hanke-unable-to-rename-a-jira-local-user-no-option#

-wc

Hi William, thx for your quick reply. Well, I have tried that already. Please have a look at the attached screenshot. There is no 3rd field available...

Any Ideas?
Martin