Another JCMA error encountered while migrating Boards:

2025-09-22 13:58:45.039908678 ERROR CROSS-PROJECT-DATA project-export : The Board 'Continuous Integration' is assigned invalid administrators:''. [JCMA 124] Use the troubleshooting page to fix this error. Open the troubleshooting page using the URL below and use the error code (starts with “JCMA”) from the error to locate the fix in the troubleshooting page.
https://support.atlassian.com/migration/docs/troubleshoot-migration-with-jira-cloud-migration-assistant/#Data-preparation-errors

The problem

As the message says, there are Boards with blank or otherwise invalid administrators. These can be identified in the database with:

SELECT rv."ID", 
       "NAME",
       cwd_user.active,
       ba.*
FROM "AO_60DB71_RAPIDVIEW" rv
LEFT  JOIN "AO_60DB71_BOARDADMINS" ba ON ba."RAPID_VIEW_ID" = rv."ID"
JOIN app_user ON app_user.user_key=rv."OWNER_USER_NAME"
JOIN cwd_user USING (lower_user_name)
WHERE ba."RAPID_VIEW_ID" IS NULL;

(Postgres syntax)

It's not even possible to edit these Boards in Jira, so the fix has to be made in the database.

The fix

We're going to have to insert some 'administrator' records for Boards that lack them, to make ourselves the administrator.

Step 1: figure out your 'user key'. This is possibly  the same as your username, but equally likely to be something like JIRAUSER1010772 . This is how one can figure out one's user key, given an email address:

redradish_jira=> select distinct app_user.user_key from app_user JOIN cwd_user USING (lower_user_name) where email_address='jeff@redradishtech.com' and active=1;
┌──────────┐
│ user_key │
├──────────┤
│ jturner  │
└──────────┘
(1 row)


Step 2: insert an administrator record for each Board that lack them. Substitute your user key for 'jturner':

begin;
INSERT INTO "AO_60DB71_BOARDADMINS" ("KEY", 
                                     "RAPID_VIEW_ID",
                                     "TYPE")
SELECT 'jturner',
       rv."ID",
       'USER'
FROM "AO_60DB71_RAPIDVIEW" rv
LEFT  JOIN "AO_60DB71_BOARDADMINS" ba ON ba."RAPID_VIEW_ID" = rv."ID"
JOIN app_user ON app_user.user_key=rv."OWNER_USER_NAME"
JOIN cwd_user USING (lower_user_name)
WHERE ba."RAPID_VIEW_ID" IS NULL;
commit;

In my experience Jira does not need to be restarted after this change.

See also: