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

when a new issue is created, the email is not sent to the client (reporter)

Dario Alarcón_opetk4

Hello community, I am writing to you because I have a question.

I have a project in which when a new issue is created, the email is not sent to the client (reporter), however the assignee receives it correctly. When the issue is generated in the name of a project Admin, the email arrives correctly, the same does not happen with the clients.

Context:
The issue is created by an automation with the following characteristic:

I clarify that the automation is working correctly, the problem is that the reporter does not receive the email when the issue is created. Customer notifications are enabled

I hope you can help me solve it, thank you very much!

Accepted answers

Joseph Chung Yin

@Dario Alarcón -

The issue with your automation is that your automation created the issue, so the actor of the rule is initially set as the issue reporter. Afterward, you edit the issue. The edit issue event may not trigger a customer notification.

Please advise who is the rule actor. Once when the issue created, who is listed as the reporter.

Once we obtain those information, we can assist further on your ask.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

All comments

Joseph Chung Yin

@Dario Alarcón -

Please advise who is the rule actor. Once when the issue created, who is listed as the reporter.

Once we obtain those information, we can assist further on your ask.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

Dario Alarcón_opetk4

@Joseph Chung Yin

Thanks for you reply.

- The actor rule is "Automation for Jira".

- Once when the issue created, the reporter is a customer.

Joseph Chung Yin

@Dario Alarcón -

After looking at it further, you should use the action instead of "create issue"

It is because only at the issue creation time, if the issue has a valid request type, then it will be visible to the reporter of the issue. By default, when one creates an issue for the JSM project, he/she uses the portal UI and select the appropriate request type to create the issue.

So this means that when your issue is created via the automation rule, it will already be valid/visible to the reporter in the portal - thus the notification will go out to the reporter. Lastly, you don't need to edit the request type at the end of your automation rule.

Hope this helps. Give it a try.

Best, Joseph

Dario Alarcón_opetk4

@Joseph Chung Yin Thank you very much, it really helped me solve my problem!
You're the best.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management