What is the impact of renaming Jira users on Portfolio users and permissions?
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Purpose
When planing a mass user renaming activity in Jira, you may wonder whether your Portfolio users and plan permissions will be impacted.
Solution
It is totally safe to rename your Jira users without any impact on Portfolio. We will explain this below:
Impact of user name change on the database
Renaming users in Jira or in an external directory makes the change to the cwd_user table.
However, if you look at the jiraissue table for instance, the username in the reporter and assignee columns does not change.
This is because the those columns use the user key which is the very first username of the user when they were added to Jira.
The mapping between the user_name in cwd_user and the user key is stored in the app_user table.
Impact on Portfolio users
The value stored in the JIRA_USER_ID column of the AO_82B313_PERSON table for Portfolio is the same as user_key column from the app_user table.
The value in this column will never change as a result of a Crowd user name change.
Was this helpful?