I noticed that his happens on our support project:
Note: Reporters are different people, just hid their names out of privacy. This usually happens when a lot of people reply to the same email. Almost as if the email shot out from Jira does not keep the issue key in the subject.
Is there a way to avoid this? I tested on my end, and when I open an issue, and reply to it, all the emails stay in the issue.
I am not sure if our customers are not really following this, or what is going on really (and I don't think I can ask our customers to check what's going on). So my question to you is: Is anyone experiencing the same behaviour? If so, how did you solve it?
Thanks a lot in advance!
I suspect what is happening here is that customers are opening a ticket via email and their carbon copying other customers. When they do that the first issue was created as expected. However other customers are replying to that original email. As a result those replies are seen as new issue reports. If the customers were to reply to the Jira notification then it should result in a comment in the original ticket.
There is a lot of discussion around this topic and Atlassian is working to improve the behavior. There are a number of post in the Community on this topic so I suggest a bit of searching. Here is one article that might be of use - Quickfix-Solve-Duplicate-Tickets-from-Email-Replies-with
Hello Community! Quick disclaimer: We are running a contest on Community (The Atlympics!) from July 23rd - August 8th of 2021. If you are interested in participating in this contest (prizes! ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events