Jira export/import should use the account id to follow the username deprecation process

Problem Definition

As a Jira administrator, I CSV exported a list of Jira issues through the advanced search in order to later import this data using the CSV external system importer.

If a comment is among the data exported, the commenter is presented in the CSV file with the username value.

Since the username is getting deprecated as per Deprecation notice and migration guide for major changes to Jira Cloud REST APIs to improve user privacy. We should have a replacement for this value.

Suggested Solution

Export the account id value rather than the username.

Why this is important

Currently, the external system importer cannot identify the account id value if set in the CSV file. If the username gets deprecated the import process will get broken.

Workaround

You may use the email address instead of username or account ID to identify the users.

 This workaround does not work for custom fields yet.