Issue Summary

Adding a new board admin to a board will result in an insert using the external_id as the "KEY" column value in the "AO_60DB71_RAPIDVIEW" table.

Reproducible on Data Center:
No, Datacenter uses user_key.app_user

Steps to Reproduce

1. Create a new user;
2. Create a new board;
3. Add this user as a Boardadmin;
4. Run the following query to retrieve all board names and admins:

   select ad."NAME", ad."OWNER_USER_NAME", adb."RAPID_VIEW_ID", adb."KEY" from "AO_60DB71_RAPIDVIEW" ad
   join "AO_60DB71_BOARDADMINS" adb on adb."RAPID_VIEW_ID" = ad."ID"
   

5. The latest entries in this query are showing an external_id in the "KEY" column:
   

Expected Results

Jira should use user_key for all user associations.
During the export, the external_id's should be replaced with user_keys, so that board admins will work as expected once migrated to Data Center.

Actual Results

external_id is used.
While the Cloud instance is able to understand the external_id as the user profile, DC is unable to create such an association. User references are made to the user_key which is then tied to the cwd_user table to retrieve the user profile.

This is a critical problem during migrations from Cloud to Data Center. This means once the data is migrated to DC, most boards will lose their administrators and there is no easy way to identify the users without database manipulation.
This happens because the external_id is not used for user profile associations in DC, it uses the user_key instead. That being said the "AO_60DB71_BOARDADMINS" will show anonymous users after the migration:

This will impact any Cloud to DC migration.

Workaround

No workaround is available.