You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
DON'T WANT = New tickets created via emails sent to our email address.
WANT = Customer email reply to question sent from JSD issue to log a comment in the issue.
WANT = Customer email reply to a notification sent from JSD issue to log a comment in the issue.
Business Goal = We want to force the user to fill out a number of fields on the request / issue record. This level of details would not be obtained from a ticket automatically created from a received email.
Welcome to the Atlassian community!
I believe the functionality that you are looking for is built-in features in JSM (Jira Service Management) (previously known as JSD (Jira Service Desk)).
To disable any requests created from your JSM email channel, you can go to Project Setting -> Email Requests. Click the triple dots on the top right of the page. Click "Disable all email requests". Then, all emails sent to your JSM email channel will be ignored.
Depending on your Notification Scheme configuration, the customer will receive a notification from Jira when, for example, an issue is updated. To add a comment to the issue, the customer can reply to the email notification directly, without a need to go to the JSM portal. The email body content will be added as a comment on the issue.
Additionally, if the customer would like to add a user as the participant of the ticket, the customer can add the user's email address to the "cc" of the email. Jira will automatically add the "cc" email addresses as the Request Participant of the issue.
For more info, please refer to https://support.atlassian.com/jira-cloud-administration/docs/create-issues-and-comments-from-email/
I hope the above answer helps!
Regards,
Marini
Thanks @Marini Marini for your feedback.
One question, is you disable all email requests, in order for all emails sent to JSM email channel to be ignored. The replies to jira email notifications will be taken in as comments or not?
Thanks
Sebastian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The replies to the Jira email notification will still be taken in as a comment. This process is handled by Jira notification and it is not related to the JSM Emailed Request setting.
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.
I have just tested. Disabled Email request and after that client's email reply is not added as comment :(
@Sebastian Delmastro does it work for you?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @REG23
Check your site's JSM global setting https://<your-site>.atlassian.net/jira/settings/products/jira-service-management-configuration. Check if the setting for Email is "Yes, allow all emails that contain a valid issue key to be added as a comment to the issue". Then, try again.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I did change this setting, and still was not receiving comments via customer's replies
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The above-mentioned suggestion of disabling JSM email requests won't actually work - the system will not create new requests but also won't leave replies as comments. We've had a few of the same requests as the original question status and I have not found a built-in solution for this.
Anyhow, we have made a 'workaround' for this by using automation - whenever a new issue is created (request type = emailed request) automatically close the issue and leave a comment that points the user/requester to use the JSM portal/help center, together with the link to the portal.
This was actually really adopted by all of our clients that wanted to transition from using emails to using JSM and it proved to be quite efficient as well.
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.