This has happened to us multiple times, and I cannot figure out where to check or alter settings. The most recent example is similar to this:
To be clear, these are new emails - not forwards or replies to previous email chains.
We have also had this happen multiple times with HR emails with subject lines "New Hire Notification - Firstname Lastname, DD/MM/YY" when the names and dates were different.
I cannot figure out if there is a setting with the email handler to prevent this. I thought the default behavior was for Jira to only add emails as comments when they contained a valid issue key.
Hi @Robert Hook
Please check if any of the incoming mail handlers are interfering with the service management email request setup.
You can check the mail handlers from the link - https://<xxxx>.atlassian.net/secure/admin/IncomingMailServers.jspa
@Bhanu This is what I am seeing. I did not set up or help configure our Jira instance (I just inherited it), so I am not entirely sure what I am looking for.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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/Jira-Ticket-from-email-does-not-create-a-new-ticket-it-only/qaq-p/2329296#U3167914
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.