Cloning an issue that contains a user mention in the description field generates an inaccurate email notification

Summary

Having an issue with a description field where another user mentioned your user as an update of the field, when you later try to clone the issue, since the description field will be cloned, all its content will be cloned, you will get notified by email that you mentioned yourself in an issue.

Steps to Reproduce

1. Create an issue with a description field.
2. Another user updates the description field and mentions your user as part of the update. (you can get notified that an update was made in the issue, this is not our case study here)
3. When you try to clone an issue.
4. When your profile is configured to not receive changes you make. (This step is very important otherwise the behaviour won't be replicated)
5. You will not receive an email telling you that the new issue let's call it "clone - Issue" was created.
6. However you will receive an email telling you that you mentioned yourself in an issue. (which is not true because another user originally mentioned you)

Notes

• this only happens if the configuration in your profile is to not notify you of your own changes
• If the notify you of your own changes is activated, when you clone the issue, you will receive one email telling you that an issue was created.

Workaround

• When the notify you of your own changes is activated in the profile config you receive accurate email notifications, this may be considered a workaround.