The migration to Jira Cloud will not wipe project's custom email address configured on Server

Summary

Both in Jira Server and Cloud, it's possible to configure a "project outgoing email address" in the project's notification scheme. As in Jira Server, users have to configure their own SMTP server to send Jira notifications, no validation is made towards the address set in the notification scheme. However in Jira Cloud, to use a custom email address, users have to verify their domain and add DKIM/SPF records to their DNS.

Recently, the Jira Cloud import is no longer replacing the project's email address with the cloud one, which bypasses the DKIM/SPF validation.

Steps to Reproduce

1. On a Jira Server, configure a custom email address in the notification scheme.
2. Export the XML Backup
3. Import on Jira Cloud

Expected Results

The project's custom email address is replaced with jira@<site>.atlassian.net

Actual Results

The custom email address is imported over.

Notes

A side effect of this bug is that Jira emails will be rejected by remote mail servers, as Atlassian won't have the necessary permissions to send emails on behalf of the custom domain.

Workaround

Validate the domain as per https://confluence.atlassian.com/adminjiracloud/configuring-jira-cloud-to-send-emails-on-behalf-of-your-domain-900996548.html