Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

How to have automatic addition of an email signature for any comment on the Jira ticket?

Edited

Issue:
Recipients email back to a Jira (...atlassian.net) notification email which is not monitored and so was missed.

Background:
When a Jira user emails to customer. On the Customer's Outlook, the email displays as below. Please note From Email has the <Jira User Name> (redacted) along with notification email. Customers assume this is the email to reply back to us which is incorrect.

image_480.png

Resolution(s):

  • Any workarounds are welcome.
  • Our suggestion is to have a message included in auto email signature added for each reply, however, this feature is not available apparently.

1 answer

0 votes
Joseph Chung Yin
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 23, 2023

@Support Programmer -

A typical setup in JSM as described - https://support.atlassian.com/jira-service-management-cloud/docs/how-do-customers-send-requests-by-email/ will retreats any reply to noticiation as a comment to the issue.

Please review the following link to ensure your JSM mail handler is setup correctly - https://support.atlassian.com/jira-cloud-administration/docs/create-issues-and-comments-from-email/

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

Hi @Joseph Chung Yin ,

Thanks for your prompt response. Yes, we confirm that JSM mail handler is setup correctly and the JSM typical setup is followed by us and our customers for almost 90% of cases.

From the steps below from the link shared to us:

  1. A customer emails a request to your service project’s email address. The request becomes an issue in your service project and is added to a queue.
  2. An agent comments on the issue.
  3. The customer receives an email notification that contains your agent's comment.
  4. The customer replies to the email notification and the reply displays as a comment on the issue in the service project.

image.png

When the agent comments on the issue, the customer receives an email notification.

If a customer replies to that email, no problem.
But some of our customers assume Sam.. <jira@CompanyName.atlassian.net> to be the agent's email and they send/reply to it. This is our problem.

Joseph Chung Yin
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 23, 2023

@Support Programmer -

So, your customers are receiving multiple notifications for the same issue key from agent?

Typically, there should just be one notification received by your customers.  Can you confirm if the customers are receiving multiple notifications?

Best, Joseph

HI @Joseph Chung Yin ,

Answering your question:
No, they are not receiving multiple notifications for the same issue key from agent.

They receive the notification email in their Mailing App (i.e. Outlook) when we (agent) respond to them in JSM ticket.

When they reply back from Outlook to the correct email address, it is recorded in JSM ticket.
However, if they reply to the 'Jira Notification Email Address' (since agent's response is sent out to them with 'Jira Notification Email Address' as Sender), this is when these (customer) emails get missed.


Please let me know if it was not clear, I am happy to rephrase. :)

Joseph Chung Yin
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 24, 2023

@Support Programmer -

Hi Sam:

What do you mean by "reply back from Outlook to the correct email address" vs reply to the "Jira Notification Email Address'"?

Can you provide examples for clarification?  For some reasons I am not seeing the issue if customers just reply on the notification that he/she received.

Best, Joseph

HI @Joseph Chung Yin ,

"reply back from Outlook to the correct email address"  means:
Customer replies to our Customer Service Email Address.
[This is when Customer clicks on 'Reply' or 'Reply All' button in Outlook App.]

"reply to the "Jira Notification Email Address" means:
[Customer views the Sender Email Address (i.e. the email address shown below) and sends their reply to this email address.]

image.png

 

Please let me know in case of any more doubts. Thank you.

Joseph Chung Yin
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 25, 2023

@Support Programmer -

Unfortunately, that is how it works by default.  Each email has additional hidden data/ID/tread references.  So when one reply back using the notification message, it correctly add the reply as a comment.

However, if one sends a message using the address, it will not work.  It is because there are no references (in the hidden data of the message associates back to the original issues).  It treats the email as brand new email.

If you have question on the default behavior out of the box, then you will need to contact Atlassian Support (https://support.atlassian.com) to see if they can open a product enhancement request for you.

Hope this helps.  If my suggestions so far helped you, please click on Accept answer when you have a chance.

Best, Joseph

Hi @Joseph Chung Yin ,

With that being said, could you please advise if there is any workaround for avoiding or at least mitigating this customers' mistake?

Hi @Joseph Chung Yin ,

Considering there was no update, I assume that only workaround is to raise a feature request/suggestion.

This question can be closed if the above is true.

Joseph Chung Yin
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 05, 2023

@Support Programmer -

Sorry for the delay on replying back to you.  Yes, unfortunately I am not aware of any workaround available.  Hopefully, Atlassian Support can add your ask as an enhancement for their product in the future.

If all of my suggestions helped you, please click on "Accept answer" when you have a chance, so others with similar asks can see this post as an answered one.

Best, Joseph

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events