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; } } }

Jira service desk issues create new issue on reply to email

Andrew Knight_4shu5r

Hi,

We're having a similar issue where some (not all) emails where they're replies to the Jira Emailed notification, are creating new tickets rather than linking to the issue as a comment.

However I don't believe that your permission answer applies here, as I was able to replicate it with my account and I definitely have permission as one of the administrators of the Service Management Project.

For elaboration, Client Raised a ticket > Team fixed the issue and closed the ticket > Client replied to me specifically (not service desk) > I readded the service desk email and replied to him. This then created a new issue, rather than add the comment, however the issue key was always present in the subject line.

Is there more details/requirements you can provide on exactly what the system uses/looks for when matching emails to issues.

Thanks
Andrew

Accepted answers

Liam Green

Hi @Andrew Knight

You were not the reporter in the above scenario, so when you replied I think the service desk would see you don't match the reporter and create a new ticket.

All comments

Liam Green

Hi @Andrew Knight

You were not the reporter in the above scenario, so when you replied I think the service desk would see you don't match the reporter and create a new ticket.

Andrew Knight_4shu5r

Hi Liam,

That seems like an odd way to process the tickets, that the only people that can comment by email are the reporter and the assignee. And that anyone else that wants to comment would have to open up the ticket rather than replying to the email.

I'll look further into it but I cannot see this as the reason why.

Thanks
Andrew

Liam Green

Hi Andrew

The other people who can comment are request participants, but it is possible that you weren't a request participant - which is why a new ticket was created.

Andrew Knight_4shu5r

Hi Liam,

That makes more sense, but to have such a restricted criteria seems disadvantageous, particularly when the ticket code is in the subject line.