Summary
Remap and preserve "Issue History" attribution when merging Atlassian user accounts via the standard SOP or Merge Accounts early access program.

Description
Currently, when customers follow the standard operating procedure for [Merge user accounts | Atlassian Support|https://support.atlassian.com/migration/docs/merge-user-accounts/], certain historical data points are not remapped to the new destination account. Specifically, the "Issue History" (the chronological log of changes made to a Jira issue) remains associated with the original account ID or becomes disconnected, rather than being attributed to the new merged identity.

For customers, maintaining a complete and accurate audit trail is critical for compliance and traceability. When project content is migrated, and accounts are consolidated (for example, moving from legacy domains to a primary corporate domain), the loss of attribution in the Issue History tab creates gaps in the digital record of who performed specific updates.

Current State

• The account merge process successfully handles many attribution points (like Reporter and Assignee in some contexts), but Issue History is not currently supported for remapping.

• Historical updates in the "History" tab of Jira issues still point to the old/unlicensed account or lose the direct link to the active user profile after a merge.

Desired State

• The account merge/mapping process should include a comprehensive remapping of the Issue History table.

• All historical actions (field changes, status transitions, etc.) performed by the source account should be visually and programmatically attributed to the destination (merged) account.

• This ensures that the "digital history" remains intact, accurate, and traceable to the appropriate individual regardless of email domain changes or account consolidations.