Problem Statement

During Jira Cloud-to-Cloud (C2C) migrations, the migration tool copies change history in "change groups", bundling multiple related change items together. If any change item within a group references a non-existent entity (such as a missing custom field option, status or attachment), the entire change group is skipped during the import. This results in incomplete historical data, leading to gaps in issue history and reduced user context in the migrated environment.

Proposed Changes

• Individual Change Item Migration: Enable the migration tool to process and migrate individual change items within change groups, allowing for valid change items to be transferred even if some items are missing or inconsistent and reducing the possibility of historical data loss.
• Migration of Text Strings for Broken References: Implement functionality to migrate the text strings displayed in the Jira UI for historical changes, even when references to underlying entities are broken. This would preserve the context of changes as users see them in the source environment.

Current Workaround

Currently, users can utilize the Jira REST API to manually extract detailed issue data, including activity and history. Alternatively, some third-party Jira Marketplace Apps can assist in exporting detailed issue data.