Tempo Ideas

Use Case

Migrating projects between Jira Data Center instances, including Tempo accounts and worklogs.

Pain Point

When migrating issues and then importing Tempo accounts via CSV:

• Accounts in the target instance receive new IDs

• Issues still reference old account IDs

• Old IDs are often incorrectly matched to new accounts
  → Issues and logged hours end up linked to the wrong account

Updating the account on the issue does not reassign existing worklogs.

Proposed Solution

Allow account mapping during migration/import to use the Account Key instead of the Account ID.

Benefit

Since the Account Key remains consistent across instances, this would ensure:

• Correct account assignment

• Preserved worklog associations

• Reduced manual post-migration fixes