要約

Check what to do when you see the warning message "WARNING <pkey> project-import We couldn't import Change Group".

概要

When migrating projects from on-premise to the cloud with the Jira Cloud Migration Assistant (JCMA), the below warning messages are present in different log files:

WARNING <project_key> project-import We couldn't import Change Group <change_group_id>. Reason: jira/classic:project:<project_id>, jira:projectComponent:<component_id>...

The Jira changegroup table tracks the change history on Jira Issues along with the changeitem table, so when we migrate Change Groups, we are migrating pieces of this history.

It's common for some of the Change Groups items to fail during the migration, as the issue history could refer to an entity that was deleted from the instance or even an entity not scoped in this migration plan.

Since the reference doesn't exist, the JCMA can't link it to the Jira Issue correctly and raises this warning, saying this entity was not migrated due to a missing dependency.

ソリューション

There are two parts to it:

Identify the missing entity

Using as an example the "Reason: jira/classic:project:<project_id>" from the warning message above.

This indicates that the Change Group has not migrated since the piece of history of the Jira Issue involved in this project.

Since the entities are referenced by ID, we recommend getting more information from these entities from the database.

Below are some queries that you can use based on the entity in the warning message:

-- Reason: jira/classic:project:<project_id>
SELECT * FROM project WHERE id = <project_id>;

-- Reason: jira:projectComponent:<component_id>
SELECT p.pname, c.* FROM component c JOIN project p ON c.project = p.id WHERE c.id = <component_id>;

-- Reason: jira:projectVersion:<projectVersion_id>
SELECT p.pname, pv.* FROM projectversion pv JOIN project p ON p.id = pv.project WHERE pv.id = <projectVersion_id>

-- Reason: jira/classic:permissionScheme:<permissionScheme_id>
SELECT * FROM permissionscheme WHERE id = <permissionScheme_id>;

Scope or Ignore

If you identify the entities in the Reason part of the message not scoped in the migration plan, you can scope them so that such Change Groups are migrated.

If you identify the entities no longer exist in the instance, you can ignore this warning message.

When the entities don't exist in the UI, they are already inconsistent in the source instance, and this isn't a blocker for the migration.