Jira Ticket from email does not create a new ticket, it only appends the old ticket.

[jmercado]

Hello All,

Does anyone of you encountered or experienced this?

For example, I would send an email to external client and I would cc my JIRA email because I want it to auto creates a ticket in my JIRA project.

My subject for example is: Vendor Set Up  SAP - ABC Company. It will create a ticket afterwards. 

However, when I send a new email for another vendor, my subject would be "Vendor Set Up  SAP - XYZ Company". I noticed that instead of creating a brand new ticket since the subject is unique, it only appends the other ticket which is for the XYZ company. So now my email to the other vendor (xys) is being added (as a comment) to the previous ticket (abc company). 

Do you know why this is happening and how can I counter this?

My email subject works like a template but the company name keeps changing, so that should be separate ticket for each. 

Can you share some thoughts on this, please?

Thanks,

J Mercado

[Ryan Barrett]

Seemingly still happening. We saw something similar the other day. 

Issue key not in subject or email. 

The common theme I'm seeing is emails with subjects "Do Something XYZ" and "Do Something ABC" Could become a comment on the previously created ticket.

I'm totally guessing... it might be looking at the first couple words to attach to a previous ticket with similar words at the beginning.

However, We have Dozens of duplicate subjects and I'm not sure we've seen this before...

another instance of this issue: https://community.atlassian.com/forums/Jira-Service-Management/New-email-with-no-issue-key-is-adding-comments-to-resolved/qaq-p/2832497

[Joseph Chung Yin]

@jmercado -

Based on my experience, your custom email handler setup should works as defined in the following Atlassian documentation - https://support.atlassian.com/jira-cloud-administration/docs/create-issues-and-comments-from-email/  (Look for the section starting with "Custom email handlers"

Please look at your custom email handlers configurations to detect the possible problem.  In your described case, the email to become a comment of an existing issue is because the issue key is found in the email subject line.

Hope this helps

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

[jmercado]

Thank you. I am using Issue Key and it works for some of my emails. but if I am not using an issue key (since it's fresh email), then there is nothing to detect yet, supposed to be. That's why I am confused why it is going to the ticket when I am not adding issue key in the email subject.