COMMENTING INSTEAD OF CREATING NEW ISSUE

[Compliance Grupo Vertical]

Jira is considering incoming emails sent by the same person and commenting on old issues instead of generating new issues

[John Funk]

Hi @Compliance Grupo Vertical  - Did you ever get this resolved? 

[Trudy Claspill]

Hello @Compliance Grupo Vertical 

Welcome to the community.

Do the emails have the same content in their Subject lines?

Is the email going to a Service Management email address or a general email handling configuration for Jira?

[Compliance Grupo Vertical]

In some cases the subject is very similar! The email going to a Service Management email address

[Trudy Claspill]

Are the users using the Forward option on previously sent messages, then modify the Subject/Content to be slightly different and then sending those messages?

Or are the users creating brand new emails from scratch and those emails are ending up as Comments?

If a users starts a new email by using the Forward option on a previously sent message and then modifies the content, Jira will see extrapolate from the email header and info in Jira about processed emails that the new email relates to an email it already processed, and treat the email as an addition to an existing issue even if the Subject has been changed. 

Users need to make sure that they are starting with a brand new email, and that the email Subject is not a copy of an email previously sent to Jira.

[Compliance Grupo Vertical]

The users  are creating brand new emails from scratch and those emails are ending up as Comments

[Nic Brough -Adaptavist-]

You'll need to educate your users not to use issue keys in their email subjects.  That's all Jira is looking for when it reads an incoming email.

If it doesn't find a valid issue key, it will create a new issue in the defined project.