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 ?
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
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 ?
You should use REST, as advised. Modifying the database directly when there is a perfectly good *supported* way to accomplish what you want is needlessly reckless. However, if you stubbornly and against all sane advice insist on manipulating the data directly, the impact should be limited to app_user.lower_user_name, the cwd_user name columns, and the cwd_membership child_name and lower_child_name columns for those with a membership_type of CWD_USER. All the others should remain the user's key -- that is the whole point of the rename user work we did in 6.0.
REST is a plugin, but it is included with JIRA, not one you would have to download and install separately. You can read more about what REST is and walk through a few tutorials about it here: https://developer.atlassian.com/jiradev/api-reference/jira-rest-apis
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.
Granted, Atlassian advises against the use of SQL to manipulate user tables.
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.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG