Missing Fix Version and Component Fields Post Jira Cloud Migration
Platform Notice: Cloud Only - This article only applies to Atlassian apps on the cloud platform.
Summary
After migrating projects to Jira Cloud using the Jira Cloud Migration Assistant (JCMA), you may notice that some issues are missing values in the Fix Version and Component fields. This article explains why this can occur and how to identify and address the issue.
Diagnosis
To identify the cause in your environment, you can run the following query on your Jira Server or Data Center database. Replace <id of the project> with the project ID you want to check:
SELECT
c.id as component_id,
c.cname as component_name,
c.project as component_project_id,
CASE
WHEN c.project = <id of the project> THEN 'TO BE EXPORTED'
ELSE 'TO BE FILTERED OUT'
END as migration_status
FROM jiraissue i
JOIN nodeassociation na ON na.source_node_id = i.id
JOIN component c ON na.sink_node_id = c.id
WHERE i.project = <id of the project>
AND na.association_type = 'IssueComponent'
ORDER BY migration_status, c.cname;If any components or fix versions are associated with a different project ID, they will be filtered out during migration, resulting in missing values in the migrated issues. You can also retrieve the issues with their component IDs using the following query. Replace <PKEY> with your project key:
select ic.component, c.cname, CONCAT(ji.pkey,'-', ji.issuenum ) AS issuekey
from jiraissue as ji
left join issuecomponent as ic on ji.id = ic.issue
left join component as c on ic.component= c.id
Where pkey = '<PKEY>'Cause
This issue typically occurs when the components or fix versions associated with an issue belong to a different project than the one being migrated. The migration tool intentionally filters out components and fix versions that do not belong to the issue's current project. As a result, these fields may appear empty after migration.
Solution
Correct the component and fix version associations on the server before migration, ensuring they belong to the correct project.
Manually update the affected issues in Jira Cloud after migration.
If you have further questions or need assistance, please contact Atlassian Support.
Was this helpful?