Hi,
We have lot of usernames with their mail address and now we have to update the domain name of all those user accounts.
So we need the list of tables to modify for a successful username update ?
Best Regards,
Nithin CK
Actually, there is also data on app_user. Still, I would not recommend doing this - rather, modify these usernames by editing the users in JIRA. If multiple users need to be edited, use a script to update them through REST: https://docs.atlassian.com/jira/REST/latest/#d2e4140
Hi Nithin!
All information regarding users in JIRA (at least on the most recent versions) is distributed between two tables: {{cwd_user}} and {{cwd_membership}}.
--Cheers!
Joao
Hi Joao,
Thanks for the quick response.
Actually I modified the usernames in all these below tables and attributes in the image but still we faced few problems like dashboard was not accessible, filters were not available.
So we need to know if we have missed anything else in our procedure ?
SQL_Tables_List.jpg
~Nithin CK
Nithin, The thing is, not all of those will need to be changed. Most of those are associated with the user's user_key (from app_user) and not with the user_name from cwd_user. That's likely the reason this is breaking.
Those should not be changed, the user_key should always remains the same. In order to maintain the integrity of the database I'd definitely advise you to use REST or the UI.
Hello Nithin,
what is you JIRA version?I've done a complete rename of all JIRA users over 3 directories (internal, 2 different active directories). Some internal users where also in these active directories with different usernames. This was done against JIRA 6.0 and at this version there was no offical rename feature.
Regards,Tim
Granted, Atlassian advises against the use of SQL to manipulate user tables.
In at least the case of https://answers.atlassian.com/questions/250787 and my case, using the UI (or REST) does not work (see https://jira.atlassian.com/browse/JRA-45203)
Tempo users had this problem here: https://tempoplugin.jira.com/browse/JTMPO-1100
Atlassian acknowledge this in https://jira.atlassian.com/browse/JRA-36642 - this is reported to be fixed in JIRA 7.
It looks like you're new here. Sign in or register to get started.