Issue Summary

When cloning an Issue, if a scenario where the legacy template notification is used - using a custom FROM or domain for example - the reporter sent in the email body with the message "<user> created an issue" is set with the original ticket reporter instead.

However, the Issue is cloned with the correct reporter User - the one who cloned it.

This is reproducible on Data Center: (yes) / (no)

Steps to Reproduce

• Setup project notification settings so that an issue create email will satisfy an exclusion reason

• Clone an issue where the user performing the clone a) has modify reporter permission and b) is different from the reporter for the original issue

• Observe that emails sent via the exclusion path have incorrect reporter

Expected Results

The "<User> created an issue" message should have the User who cloned the issue as the reporter;

Actual Results

The message is sent with the original Issue reporter.

Workaround

To avoid using a custom FROM/Domain on the notifications