There is JSON data showing in my responses. My customer notifications looks like this when replying:
{"@context":"http://schema.org","type":"EmailMessage","description":"View request","potentialAction":{"@type":"ViewAction","target":"https://ubmv.atlassian.net/servicedesk/customer/portal/1","name":"View request"},"publisher":{"@type":"Organization","name":"Atlassian","url":"https://www.atlassian.com" }}
—-—-—-—
Reply above this line.
UBMV Support changed the status to In Progress.
View request · Turn off this request's notifications
UBMV
Hello @UBMV Support,
Welcome to Atlassian Community!
The issue that you are facing is related to the outgoing email format. It's possible to send notifications in HTML or plain text.
To fix this issue, there are some settings that you will need to change on the site.
Please, go to Cog icon > Products > Email requests.
On this page, make sure to check the option "Enable HTML email parsing".
Then, go to Cog icon > System > Default user preferences and confirm if the default outgoing email format is set to HTML as well:
If the customer who is receiving the notification is also an internal user (for example, an internal user for Jira Software, but also a customer for Service Management), there is also a configuration that they must check on their profile, so if this is happening for a specific person, they must go to Profile picture > Personal settings > Email notification format and change it to HTML.
Regards,
Angélica
Thank you Angelica
I'm confirming that all the settings have been double checked as given by you and we still see the JSON code at the top of each email submitted from the service desk.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for checking, @UBMV Support.
Further searching about issues related to notifications, I found that this is caused by an open-source spam filter called MailScanner.
A bug was created a while ago, but this issue is not caused by Jira, so there is nothing that can be changed on our side to prevent this issue from happening.
For more details, please check the link below:
This is known to be caused by an open-source email filtering plugin called MailScanner. JIRA sends ld+json markup inside a <script> tag to support Gmail button actions, as described in their documentation. Since scripts inside of email HTML should never be executed by modern email clients, this markup should generally be used to support the Gmail client and discarded by other clients. However, MailScanner can be configured to disarm script tags, which then passes them through to email clients in plain text.
This has no adverse impact, however it distorts the final rendered email notification from JIRA. We consider this a known issue; however we have been advised by the Gmail team that there is no workaround at this time.
We recommend that customers revisit their MailScanner settings.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.