Potential bug in email notification when issues are moved

[achalker]

Select Topic Area

Bug

Body

I was encouraged by GitHub support to post this here after submitting an issue to them.

I've encountered a "bug" in the email notification system (or at least something that is designed in a very counter-intuitive way), and GitHub Support staff have been able to reproduce it.

Recently a colleague transferred an issue from one public repo to another (both repos are under the same org). Note this issue was originally created by a third person nearly 2 years ago.

I have email notifications turned on for these repos, and once the issue was transferred, I received an email notification indicating that the original third person had created the issue, which is very counter-intuitive.

I can kinda understand the logic of why this might be happening, in that the third person had indeed originally created the issue in another repo and by moving it to a second repo they should be 'credited' with creating it in the second repo.

However there was no indication in the email notification that the issue had been moved, and in fact it was very startling to me to see the notification since the person who created the issue hasn't worked with us in a very long time.

(Note there is an indication that the issue what transferred if you look at it in the web view of the repo though if you go and look at it closely)

As you could imagine, this caused some momentary confusion over whether that person was back and working on the project, and why they had created a duplicate issue to one that already existed in another repo.

Reproduction Steps

1. Have 2 repos, Repo 1 and Repo 2.
2. Ensure you are watching Repo 2 and you have email notifications turned on
3. Have Person A create an issue in Repo 1
4. Have Person B move the issue from Repo 1 to Repo 2
5. You should receive an email notification indicating Person A created an issue in Repo 2 (but not indication it was moved by Person B)

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐