Hello,
So the issue I have is that new emails are not always creating new JIRAs when they come through due to similar email subject lines.
for example each month I receive an email that has the following subject line where the ## is the version number.
Airport Operations Alert 10'16 v##
The issue is that JIRA is matching the first part of the subject to an old ticket that has been resolved and is updating it rather than creating a new ticket.
I was wondering if there is a way of updating it so that
Airport Operations Alert 10'16 v61
Airport Operations Alert 10'16 v62
would create different tickets rather than updating an existing one.
Welcome to the Atlassian Community!
What have you set up to process the incoming emails? Jira's email handlers don't do de-duplication, they always create a new issue or comment from emails.
We use Gmail.
The issue is not with de-duplication but rather with the creation of new tickets.
for example
incoming email
to: support@something.com
subject: Airport Operations Alert 10'16 v61
this will create a new jira say pro-116 and if you reply to all updates the jira created too so is working as expected.
the problem comes when a new email with the next version comes in
to: support@something.com
subject: Airport Operations Alert 10'16 v62
Instead of creating a new jira it updates the previous one so pro-116
even though its a new email thread.
I think this is down to the subject line matching within JIRA as if there is a character limit on it then it would explain why this is happening
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok, but what have you set up to process incoming emails?
A mail handler? A JSM email channel? An app?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We have a mail handler set up.
We have one entry set up for each support email address, each entry has the following items set up for it
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.