The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Service desk response email address doesn't match

Maurice Côté
February 9, 2018

Hello,

We're using the Cloud edition and have started trialing the service desk.  

When a customer replies to an email triggered by the agent asking a question, his reply opens a new ticket rather then being added to the existing ticket.

The subject does contain the ticket number, and the response was typed above the line that states

—-—-—-— Reply above this line.

 

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Jack Brickey
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
February 9, 2018

@Maurice Côté, this should not be the case. You may wish to look at this thread for more details on the designed behavior to assist w/ troubleshooting.

Maurice Côté
February 9, 2018

nice feature to prevent mishaps, but sadly for me the header is intact.

 

I have sent another reply and included another email address so I could see the raw message source

Subject: Re: DEVO-8 test
Date: Fri, 9 Feb 2018 17:01:49 -0500
In-Reply-To: <JIRA.22168.1518097464000.e378011f-0e00-4b1e-ab84-b84b0eb36434.1518097649577@Atlassian.JIRA>

So neither the subject nor the header are incorrect.

Any other ideas?

Maurice Côté
February 11, 2018

I've opened a ticket.

 

For those of you that want a summary, there is a In-Reply-To header that protects against the subject line being modified.  So in my case there are two reasons that it should work.  The ticket ID is present, and the header as well.

Here's hoping for a quick resolution....

TAGS
AUG Leaders

Atlassian Community Events