nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Mail including Jira number still creates new issue (if other sender than reporter)

Catrine Lundström

Hi,

Has anyone else experienced that new issue is created when mail is sent from other than reporter to an existing issue? Even though Jira issue number is included in summary?

We find that it happens sometimes, not always. Why?

Regards

Catrine

Accepted answers

Andrew Laden

Service desk email handlers is actually different then the core email handlers.

If the person who send the 2nd email doesn't already have access to the first ticket (ie, they are either an agent or a request participant) then they will not be allowed to add themselves to the ticket and update it. It will create a new ticket in this case.

All comments

Suhas P

I think you should try to find the pattern when it creates new emails and when comments using different users. Then you might find out why it behaves differently for some users.

Catrine Lundström

I have tried..... If you now why I guess you would tell me.... ;-)

Suhas P

Its very strang though. If you have tried multiple users, then there should be some commonalities between those users.

Jack Brickey

You might find this article interesting - how-jira-updates-issues-from-email

I have always found this function to be full of exceptions and have been unable to establish a simple answer. This article is the best attempt IMO.

Catrine Lundström

Thanks.

The article seems to cover Jira Software - we are using Jira Service Desk - but maybe it is applicable anyway?
However - it doesn't make me any wiser... ;-)